From issues at jboss.org Thu Oct 1 01:32:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Thu, 1 Oct 2015 01:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114017#comment-13114017 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- oops, [~mhusnain], I should have tagged you. I'll comment the beta topic out. Thanks - supriya > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 01:43:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Thu, 1 Oct 2015 01:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19282) Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114020#comment-13114020 ] Vlado Pakan commented on JBIDE-19282: ------------------------------------- For me exceptions in Error log are crititcal > Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette > --------------------------------------------------------------------------------------- > > Key: JBIDE-19282 > URL: https://issues.jboss.org/browse/JBIDE-19282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, MS Windows 7 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > # Create Hybrid Mobile project > # Add HTML page to www folder with this content > {code:html} > > > {code} > # Insert JS/CSS references from JQuery Mobile palette > # Insert Canvas tag from HTML5 palette inside tag > ERROR: These errors appear in Error log and no tag is added > {noformat} > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.661 > !MESSAGE Program Error: modelStateChanging was less than zero > !STACK 0 > java.lang.IllegalStateException: Program Error: modelStateChanging was less than zero > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.internalModelChanged(AbstractStructuredModel.java:825) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.changedModel(AbstractStructuredModel.java:361) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.changedModel(DOMModelImpl.java:171) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel$DocumentToModelNotifier.noChange(AbstractStructuredModel.java:139) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:513) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1172) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1959) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.676 > !MESSAGE Program Error: invalid structured document event > !ENTRY org.eclipse.wst.sse.core 4 2 2015-02-17 21:42:06.676 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.wst.sse.core". > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: assertion failed: > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) > at org.eclipse.jface.text.DocumentEvent.(DocumentEvent.java:62) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1911) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 02:20:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 1 Oct 2015 02:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-685) JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-685: ------------------------------- Component/s: General documentation issues Fix Version/s: 4.3.0.Final Priority: Minor (was: Major) Affects Version/s: 4.3.0.Final > JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide > ------------------------------------------------------------------------- > > Key: TOOLSDOC-685 > URL: https://issues.jboss.org/browse/TOOLSDOC-685 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Priority: Minor > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 02:21:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 1 Oct 2015 02:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-685) JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali resolved TOOLSDOC-685. -------------------------------- Resolution: Done Published Upgrade document without Beta information and removed Beta information from Docker article. Both are now published, with the upgrade guide being published publically on GA. > JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide > ------------------------------------------------------------------------- > > Key: TOOLSDOC-685 > URL: https://issues.jboss.org/browse/TOOLSDOC-685 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Priority: Minor > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 02:21:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 1 Oct 2015 02:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-685) JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-685: ------------------------------- Sprint: (was: 12-Oct >> 25-Oct 2015-JBDS/JBT) > JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide > ------------------------------------------------------------------------- > > Key: TOOLSDOC-685 > URL: https://issues.jboss.org/browse/TOOLSDOC-685 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Priority: Minor > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 02:21:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 1 Oct 2015 02:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-685) JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali closed TOOLSDOC-685. ------------------------------ > JBDS 9: Remove mentions of Beta and CR from all docs except Install Guide > ------------------------------------------------------------------------- > > Key: TOOLSDOC-685 > URL: https://issues.jboss.org/browse/TOOLSDOC-685 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Priority: Minor > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 02:22:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 1 Oct 2015 02:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-683: ------------------------------- Component/s: General documentation issues (was: Release Notes) > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 02:22:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 1 Oct 2015 02:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-683: ------------------------------- Labels: Configurations Supported (was: ) > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 02:23:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 1 Oct 2015 02:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114034#comment-13114034 ] Misha Ali commented on TOOLSDOC-683: ------------------------------------ Thanks, guys. [~mmalina], any thoughts on when/if verification will be available by QE for 3.9.0^? I'll wait for the answer and update these tomorrow. > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 04:05:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Thu, 1 Oct 2015 04:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3534) Provide UI to see/export Central configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114048#comment-13114048 ] Radim Hopp commented on JBDS-3534: ---------------------------------- Good idea! > Provide UI to see/export Central configuration > ---------------------------------------------- > > Key: JBDS-3534 > URL: https://issues.jboss.org/browse/JBDS-3534 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > Affects Versions: 8.0.2.GA, 8.1.0.GA, 9.0.0.GA > Reporter: Denis Golovin > > In current and previous releases it is not possible to investigate issues reported against Central, because of configuration complexity which involves to many local and remote resources. Would be good to have some sort of UI that would let to see what is actually used in central to fill Software/Update tab. This way in case of issues like this JBDS-3533 we at least would have a way to see what is actually used on client side. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 04:57:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Thu, 1 Oct 2015 04:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: Pavol Srna created JBIDE-20844: ---------------------------------- Summary: kitchensink-cordova project examples are not imported into the workspace Key: JBIDE-20844 URL: https://issues.jboss.org/browse/JBIDE-20844 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.3.0.CR2 Reporter: Pavol Srna Fix For: 4.3.0.CR2 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 05:11:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 05:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: Martin Malina created JBIDE-20845: ------------------------------------- Summary: Unable to install breakpoint even if line number set to be generated Key: JBIDE-20845 URL: https://issues.jboss.org/browse/JBIDE-20845 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Affects Versions: 4.3.0.CR2 Reporter: Martin Malina I am unable to get breakpoints to work for a html5 project running on WildFly. I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. Reason: Absent Line Number Information I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: org.eclipse.jdt.core.compiler.debug.lineNumber=generate This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 05:11:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 1 Oct 2015 05:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20846) merge v2 and v3 feature pages In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-20846: ------------------------------------------- Summary: merge v2 and v3 feature pages Key: JBIDE-20846 URL: https://issues.jboss.org/browse/JBIDE-20846 Project: Tools (JBoss Tools) Issue Type: Task Components: website Reporter: Max Rydahl Andersen Assignee: Fred Bricon it is waste of valuable space to have both v2 and v3 on http://tools.jboss.org/features/ Most of the content inside are exactly the same so seem simpler to just add a "For OSv3 we have Deploy Docker ..." or some other mechanism to highlight it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 05:12:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 05:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina updated JBIDE-20845: ---------------------------------- Attachment: breakpoint-error.png > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Attachments: breakpoint-error.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 05:12:01 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 05:12:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina updated JBIDE-20845: ---------------------------------- Description: I am unable to get breakpoints to work for a html5 project running on WildFly. I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. Reason: Absent Line Number Information !breakpoint-error.png! I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: org.eclipse.jdt.core.compiler.debug.lineNumber=generate This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. I'm not really sure which component this should belong to, it looks like an upstream issue. was: I am unable to get breakpoints to work for a html5 project running on WildFly. I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. Reason: Absent Line Number Information I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: org.eclipse.jdt.core.compiler.debug.lineNumber=generate This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. I'm not really sure which component this should belong to, it looks like an upstream issue. > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Attachments: breakpoint-error.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 05:13:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 05:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina updated JBIDE-20845: ---------------------------------- Attachment: compiler-settings.png Here is my preferences: !compiler-settings.png! > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 05:14:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 05:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114071#comment-13114071 ] Martin Malina commented on JBIDE-20804: --------------------------------------- I tried to verify this, but I hit a problem I can't get around. Eclipse tells me I need to enable line number attribute to use breakpoints. See JBIDE-20845 . [~fbricon], any idea what's wrong? > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.CR2 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 07:05:00 2015 From: issues at jboss.org (Jiri Peterka (JIRA)) Date: Thu, 1 Oct 2015 07:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3518) Eclipse-cs update to 6.9.0 on JBoss Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114108#comment-13114108 ] Jiri Peterka commented on JBDS-3518: ------------------------------------ Yes, cs 6.5 (from central) was tested with JBDS 9.0.0.CR1 and 6.9 (from cs site) was tested as well. To have 6.9 in JBDS 9.0.1 is ok as current 6.5 works also just fine. > Eclipse-cs update to 6.9.0 on JBoss Central > ------------------------------------------- > > Key: JBDS-3518 > URL: https://issues.jboss.org/browse/JBDS-3518 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: 3rd-party-certification, build, central > Affects Versions: 9.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 9.0.1.GA > > Attachments: checkstyle.png > > > I've checked Release 6.9.0 with JBDS 9.0.0.CR1 and experienced no issues. > Changes since last version: http://eclipse-cs.sourceforge.net/#!/releasenotes -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 07:21:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 1 Oct 2015 07:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114115#comment-13114115 ] Max Rydahl Andersen commented on JBIDE-20845: --------------------------------------------- if you press Ok, does the breakpoint not get hit anyway ? I believe what you are seeing is the sideeffect of cdi/weld or any other proxy based framework that confuses the debugger into thinking the actual class does not have linenumbers - but it actually still works. that said, it would be nice to actually fix this somehow to not confuse users. > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 07:28:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 1 Oct 2015 07:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114119#comment-13114119 ] Max Rydahl Andersen commented on JBIDE-20803: --------------------------------------------- so is this setup still going to use the data from ide-config.properties even though values can't really be in ide-config.properties before it is live ? just checking if I grok that correctly so for now this setup is only usable for manual testing ? the new generated site won't actually automatically show up unless you use the properties ? if that is the case then sure it is closed and don't really have a good solution for scripting the *actual* release of discovery sites. They will still be manual, correct? > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 07:36:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 1 Oct 2015 07:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114122#comment-13114122 ] Max Rydahl Andersen commented on JBIDE-19568: --------------------------------------------- completely agree buttons in the toolbar are not great, but the functionality of checking for updates are relevant. > Disable the "Check for update" button while a check for update is in progress > ----------------------------------------------------------------------------- > > Key: JBIDE-19568 > URL: https://issues.jboss.org/browse/JBIDE-19568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.x > > > while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog. > In error log it was reporting this: > org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > would have expected we told the user about this error. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 07:42:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 07:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19282) Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114127#comment-13114127 ] Alexey Kazakov commented on JBIDE-19282: ---------------------------------------- [~vpakan] So, currently you see the exception (in Log) but everything else seems to work? All needed components are added to the page, etc? > Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette > --------------------------------------------------------------------------------------- > > Key: JBIDE-19282 > URL: https://issues.jboss.org/browse/JBIDE-19282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, MS Windows 7 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > # Create Hybrid Mobile project > # Add HTML page to www folder with this content > {code:html} > > > {code} > # Insert JS/CSS references from JQuery Mobile palette > # Insert Canvas tag from HTML5 palette inside tag > ERROR: These errors appear in Error log and no tag is added > {noformat} > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.661 > !MESSAGE Program Error: modelStateChanging was less than zero > !STACK 0 > java.lang.IllegalStateException: Program Error: modelStateChanging was less than zero > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.internalModelChanged(AbstractStructuredModel.java:825) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.changedModel(AbstractStructuredModel.java:361) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.changedModel(DOMModelImpl.java:171) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel$DocumentToModelNotifier.noChange(AbstractStructuredModel.java:139) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:513) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1172) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1959) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.676 > !MESSAGE Program Error: invalid structured document event > !ENTRY org.eclipse.wst.sse.core 4 2 2015-02-17 21:42:06.676 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.wst.sse.core". > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: assertion failed: > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) > at org.eclipse.jface.text.DocumentEvent.(DocumentEvent.java:62) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1911) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 07:53:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 07:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114129#comment-13114129 ] Mickael Istria commented on JBIDE-19568: ---------------------------------------- Isn't it the sane thing as regular "Help > Check for Updates" menu? If so, do we really need this additional entry-point? If it's not doing the same things, then we should at very least find out a better label then. > Disable the "Check for update" button while a check for update is in progress > ----------------------------------------------------------------------------- > > Key: JBIDE-19568 > URL: https://issues.jboss.org/browse/JBIDE-19568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.x > > > while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog. > In error log it was reporting this: > org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > would have expected we told the user about this error. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:02:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:02:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20844: ----------------------------------- Labels: (was: respin-a) > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:05:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114134#comment-13114134 ] Alexey Kazakov commented on JBIDE-20844: ---------------------------------------- Do you some errors or nothing happens when you try to import, or what? Could you please add more details? > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114134#comment-13114134 ] Alexey Kazakov edited comment on JBIDE-20844 at 10/1/15 8:05 AM: ----------------------------------------------------------------- Do you see some errors or nothing happens when you try to import, or what? Could you please add more details? was (Author: akazakov): Do you some errors or nothing happens when you try to import, or what? Could you please add more details? > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20845: -------------------------------------- Assignee: Rob Stryker > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20845: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:20:01 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 1 Oct 2015 08:20:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114138#comment-13114138 ] Max Rydahl Andersen commented on JBIDE-19568: --------------------------------------------- The help menu is not available from Central unless you go open it. If we want central to where users go and install things from why not make it easy to run check for updates ? > Disable the "Check for update" button while a check for update is in progress > ----------------------------------------------------------------------------- > > Key: JBIDE-19568 > URL: https://issues.jboss.org/browse/JBIDE-19568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.x > > > while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog. > In error log it was reporting this: > org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > would have expected we told the user about this error. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:25:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Thu, 1 Oct 2015 08:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Srna updated JBIDE-20844: ------------------------------- Attachment: screen.png > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.0.CR2 > > Attachments: screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:26:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Thu, 1 Oct 2015 08:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114141#comment-13114141 ] Pavol Srna commented on JBIDE-20844: ------------------------------------ There is nothing in the log. Please see the screenshot - the project explorer is empty. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.0.CR2 > > Attachments: screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:30:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Thu, 1 Oct 2015 08:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio updated JBIDE-20844: --------------------------------- Attachment: cordova.txt Interesting - the cordova kitchensink example files are actually installed into the workspace. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.0.CR2 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:34:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20844: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 (was: 4.3.0.CR2) > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:34:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20844: ----------------------------------- Component/s: upstream > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:37:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 08:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20844: -------------------------------------- Assignee: Snjezana Peco Other project examples seem to work fine. [~snjeza] could you please take a look what is wrong with those examples and report it upstream if needed? I hope [~rafabene] can help if there is a problem with some examples from https://github.com/jboss-developer/jboss-wfk-quickstarts > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:40:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Thu, 1 Oct 2015 08:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114149#comment-13114149 ] Supriya Bharadwaj commented on TOOLSDOC-610: -------------------------------------------- Info complete and added to the Create First Hybrid Application how-to (https://access.redhat.com/node/1518153/draft) > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 08:48:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 1 Oct 2015 08:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114153#comment-13114153 ] Max Rydahl Andersen commented on JBIDE-19944: --------------------------------------------- im battling getting snapshots restored. in progress. > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.0.Final > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-product > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:04:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 09:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114164#comment-13114164 ] Martin Malina commented on TOOLSDOC-683: ---------------------------------------- [~psrna], can you take a look and confirm this, please? Thanks! > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20760: ------------------------------- Priority: Blocker (was: Critical) > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: xtriage > Fix For: 4.3.0.Final > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:08:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20331) install grinder fails due to oomph or beaker virt slaves? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114165#comment-13114165 ] Nick Boldt commented on JBIDE-20331: ------------------------------------ [~mickael_istria] Can you branch https://github.com/jbosstools/jbosstools-install-grinder/ to 4.3.x? Then I think we can close this issue or slip it to 4.4.x. > install grinder fails due to oomph or beaker virt slaves? > --------------------------------------------------------- > > Key: JBIDE-20331 > URL: https://issues.jboss.org/browse/JBIDE-20331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > Attachments: install-grinder-fail.txt, virt1-ftl.png, virt2-ftl.png > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull} > 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:08:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 09:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114164#comment-13114164 ] Martin Malina edited comment on TOOLSDOC-683 at 10/1/15 9:07 AM: ----------------------------------------------------------------- [~psrna], can you take a look and confirm this, please? Thanks! Correction: This is actually fixed in the Final build (respin of CR2) (JBIDE-20836) and we don't have that build yet, so this will be verified once we receive the Final build. was (Author: mmalina): [~psrna], can you take a look and confirm this, please? Thanks! > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:09:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 09:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114164#comment-13114164 ] Martin Malina edited comment on TOOLSDOC-683 at 10/1/15 9:08 AM: ----------------------------------------------------------------- [~psrna], can you take a look and confirm this, please? Thanks! Correction: This is actually fixed in the Final build (respin of CR2) (JBIDE-20836) and we don't have that build yet, so this will be verified once we receive the Final build. We should receive the build today. was (Author: mmalina): [~psrna], can you take a look and confirm this, please? Thanks! Correction: This is actually fixed in the Final build (respin of CR2) (JBIDE-20836) and we don't have that build yet, so this will be verified once we receive the Final build. > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:11:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Thu, 1 Oct 2015 09:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114170#comment-13114170 ] Pavol Srna commented on TOOLSDOC-683: ------------------------------------- I need to verify JBIDE-20836 in the final build. I'll comment here once QE receives the build. > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:14:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:14:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBIDE-20803. -------------------------------- Resolution: Done No. You are not grokking it correctly. This set up can be used AS NEEDED against ANY URLs to facilitate updating the shared directory.xml files. I used it to pull the latest Alpha IS jars into the CR2 staging site. It doesn't touch the values in ide-config.properties There is no immediate plan to automatically pull from the URLs in ide-config.properties. If that plan resurfaces for 4.3.x, it's in JBIDE-20664, not this issue. Marking resolved. > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:16:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Thu, 1 Oct 2015 09:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio updated JBIDE-20760: --------------------------------- Labels: respin-a xtriage (was: xtriage) > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a, xtriage > Fix For: 4.3.0.CR2 > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:16:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20760: ------------------------------- Fix Version/s: 4.3.0.CR2 (was: 4.3.0.Final) > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a, xtriage > Fix For: 4.3.0.CR2 > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 09:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20760: ----------------------------------- Labels: respin-a (was: respin-a xtriage) > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2 > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:26:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Thu, 1 Oct 2015 09:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114183#comment-13114183 ] Len DiMaggio commented on TOOLSDOC-683: --------------------------------------- The original motivation in documenting the list of supported versions was because the newest version was not supported - https://issues.jboss.org/browse/JBIDE-20836 will resolve that issue - but, it is still worthwhile to document the supported list for the customers. Thx! > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:32:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20331) install grinder fails due to oomph or beaker virt slaves? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20331: ------------------------------- Fix Version/s: 4.3.x 4.4.0.Alpha1 (was: 4.3.0.Final) > install grinder fails due to oomph or beaker virt slaves? > --------------------------------------------------------- > > Key: JBIDE-20331 > URL: https://issues.jboss.org/browse/JBIDE-20331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: install-grinder-fail.txt, virt1-ftl.png, virt2-ftl.png > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull} > 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:32:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 1 Oct 2015 09:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20847) Only "retrieve" and "sign up here" link inside styled text should be accessible In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-20847: ------------------------------------- Summary: Only "retrieve" and "sign up here" link inside styled text should be accessible Key: JBIDE-20847 URL: https://issues.jboss.org/browse/JBIDE-20847 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR2 Reporter: Mari?n Labuda Priority: Minor In New Connection dialog are 2 styled texts with links. First one is for OpenShift 2 server selection on top saying "If you do not have an account on OpenShift, please +sign up here+." Second one is for OpenShift 3 while OAuth authentication protocol is selected "Enter a token or +retrieve+ a new one." Issue is that both are clickable whole, not just the underlined parts. Issue is also differences while mouse cursor is moving over them. Second one, about a token, has hand cursor while mouse is over the text. First one has typical cursor for text. The cursor could be: - for clickable part hand cursor - for nonclickable part arrow cursor Example of nice working text with link is link for OpenShift 3 server on top of wizard "New to OpenShift 3? Explore the +getting started documentation+." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:33:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20331) install grinder fails due to oomph or beaker virt slaves? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114190#comment-13114190 ] Nick Boldt commented on JBIDE-20331: ------------------------------------ Slip to 4.3.x / 4.4.0.Alpha1. > install grinder fails due to oomph or beaker virt slaves? > --------------------------------------------------------- > > Key: JBIDE-20331 > URL: https://issues.jboss.org/browse/JBIDE-20331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: install-grinder-fail.txt, virt1-ftl.png, virt2-ftl.png > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull} > 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:33:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 1 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20847) Only "retrieve" and "sign up here" link inside styled text should be accessible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20847: ---------------------------------- Priority: Major (was: Minor) > Only "retrieve" and "sign up here" link inside styled text should be accessible > ------------------------------------------------------------------------------- > > Key: JBIDE-20847 > URL: https://issues.jboss.org/browse/JBIDE-20847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Labels: connection_wizard > > In New Connection dialog are 2 styled texts with links. > First one is for OpenShift 2 server selection on top saying "If you do not have an account on OpenShift, please +sign up here+." > Second one is for OpenShift 3 while OAuth authentication protocol is selected "Enter a token or +retrieve+ a new one." > Issue is that both are clickable whole, not just the underlined parts. > Issue is also differences while mouse cursor is moving over them. Second one, about a token, has hand cursor while mouse is over the text. First one has typical cursor for text. The cursor could be: > - for clickable part hand cursor > - for nonclickable part arrow cursor > Example of nice working text with link is link for OpenShift 3 server on top of wizard "New to OpenShift 3? Explore the +getting started documentation+." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:33:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 1 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20847) Only "retrieve" and "sign up here" link inside styled text should be accessible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20847: ---------------------------------- Labels: connection_wizard (was: ) > Only "retrieve" and "sign up here" link inside styled text should be accessible > ------------------------------------------------------------------------------- > > Key: JBIDE-20847 > URL: https://issues.jboss.org/browse/JBIDE-20847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Labels: connection_wizard > > In New Connection dialog are 2 styled texts with links. > First one is for OpenShift 2 server selection on top saying "If you do not have an account on OpenShift, please +sign up here+." > Second one is for OpenShift 3 while OAuth authentication protocol is selected "Enter a token or +retrieve+ a new one." > Issue is that both are clickable whole, not just the underlined parts. > Issue is also differences while mouse cursor is moving over them. Second one, about a token, has hand cursor while mouse is over the text. First one has typical cursor for text. The cursor could be: > - for clickable part hand cursor > - for nonclickable part arrow cursor > Example of nice working text with link is link for OpenShift 3 server on top of wizard "New to OpenShift 3? Explore the +getting started documentation+." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:33:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-18820: ------------------------------- Component/s: devdoc > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Final > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:34:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-18820: ------------------------------- Labels: devdoc (was: ) > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.0.Final > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:38:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 1 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen reassigned JBIDE-19944: ------------------------------------------- Assignee: Fred Bricon (was: Max Rydahl Andersen) i've moved feedburner to point to tiny-man.rhcloud.com. Had to limit to only show latest 10 posts as otherwise the feed got too big for feedburner. Please verify if things work as you expect (ordering, naming etc.) > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Final > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-product > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:49:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 09:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114201#comment-13114201 ] Nick Boldt commented on JBIDE-20760: ------------------------------------ {quote} (2015-10-01 09:33:02) ldimaggi_: nickboldt, so - we will have the unused and disabled update site, yes? (2015-10-01 09:40:31) nickboldt: ldimaggi_: as documented in the JIRA, putting the feature BACK into the site means when a user installs the eclipse docker tooling feature, they get added to their list of available update sites in Eclipse (not JBDS) a new, *disabled* URL for the docker update site (2015-10-01 09:40:42) nickboldt: ldimaggi_: you already agreed to this in the jira (2015-10-01 09:40:58) ldimaggi_: nickboldt, +1 just checking {quote} Also +1'd by Alexey on the PR, so applied in 4.3.x and building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-build-sites.aggregate.site_4.3.mars/ >=123 > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2 > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:50:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 09:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: Mickael Istria created JBIDE-20848: -------------------------------------- Summary: Release publish scripts and use them Key: JBIDE-20848 URL: https://issues.jboss.org/browse/JBIDE-20848 Project: Tools (JBoss Tools) Issue Type: Task Components: build Affects Versions: 4.3.0.CR1 Reporter: Mickael Istria Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:52:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 1 Oct 2015 09:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-20849: ------------------------------------- Summary: Blank space in a New Connection dialog Key: JBIDE-20849 URL: https://issues.jboss.org/browse/JBIDE-20849 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.CR2 Reporter: Mari?n Labuda Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. !openshift2_connection_dialog.png! !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:53:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 1 Oct 2015 09:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20849: ---------------------------------- Priority: Minor (was: Major) > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Minor > Labels: connection_wizard > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 09:53:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 1 Oct 2015 09:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20849: ---------------------------------- Labels: connection_wizard (was: ) > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Minor > Labels: connection_wizard > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:05:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 10:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria reassigned JBIDE-20848: -------------------------------------- Assignee: Mickael Istria > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:05:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 10:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20848: ----------------------------------- Fix Version/s: 4.3.0.Final > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20850: ---------------------------------- Summary: target platform matrix job's install test step fails silently when using incompatible Eclipse version Key: JBIDE-20850 URL: https://issues.jboss.org/browse/JBIDE-20850 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, target-platform Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 Reporter: Nick Boldt For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: {code} [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) [p2.dir] !MESSAGE Only one of the following can be installed at once: [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) BUILD FAILED /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.60.0.Alpha1-SNAPSHOT/consoleText {code} [p2.dir] !MESSAGE Only one of the following can be installed at once: [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.50.0.Final/consoleText And yet the build is successful here: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.51.1.CR1-SNAPSHOT/consoleText This is most likely because all three configs are set to use the same Eclipse JEE bundle: {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz {code} So... I guess there are two things we need here: a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20850: ---------------------------------- Assignee: Nick Boldt > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.60.0.Alpha1-SNAPSHOT/consoleText > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.50.0.Final/consoleText > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.51.1.CR1-SNAPSHOT/consoleText > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20850: ------------------------------- Fix Version/s: 4.4.0.Alpha1 > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.60.0.Alpha1-SNAPSHOT/consoleText > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.50.0.Final/consoleText > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.51.1.CR1-SNAPSHOT/consoleText > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20850: ------------------------------- Priority: Blocker (was: Major) > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.60.0.Alpha1-SNAPSHOT/consoleText > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.50.0.Final/consoleText > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.51.1.CR1-SNAPSHOT/consoleText > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:09:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 10:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20850: ----------------------------------- Priority: Critical (was: Blocker) > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.60.0.Alpha1-SNAPSHOT/consoleText > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.50.0.Final/consoleText > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.51.1.CR1-SNAPSHOT/consoleText > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:09:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 10:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114212#comment-13114212 ] Mickael Istria commented on JBIDE-20850: ---------------------------------------- Ideally, this should get into a dedication "verify" step in the pom.xml of target-platforms. So the TP would defne what Eclipse they're meant to be compatible with, and we could have multiple streams of Eclipse with the same job config. > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.60.0.Alpha1-SNAPSHOT/consoleText > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.50.0.Final/consoleText > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.51.1.CR1-SNAPSHOT/consoleText > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:10:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114214#comment-13114214 ] Nick Boldt commented on JBIDE-20848: ------------------------------------ Loots goot. Release the kraken! Or the zip. Whatever. :D Step 2: update the jobs to use this new version & kick 'em to verify. (Don't re-enable any of the disabled ones; we can just test with the CR2 respin-a aggregates/JBDS builds.) > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:10:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:10:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20848: ------------------------------- Labels: respin-a (was: ) > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:10:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:10:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20848: ------------------------------- Fix Version/s: 4.3.0.CR2 > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 10:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20848: ------------------------------- Priority: Blocker (was: Major) > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 10:11:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 10:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114216#comment-13114216 ] Mickael Istria commented on JBIDE-20850: ---------------------------------------- This is not a blocker since we can still produce and deploy good TP. The target-platform-validation mojo gives some guarantees, and doesn't depend on the specified Eclipse version. > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.60.0.Alpha1-SNAPSHOT/consoleText > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.50.0.Final/consoleText > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/460/jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||jboss-prod%29&&!ia64&&!rhts,projectName=jbosstools,version=4.51.1.CR1-SNAPSHOT/consoleText > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:00:01 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 1 Oct 2015 11:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114236#comment-13114236 ] Snjezana Peco commented on JBIDE-20844: --------------------------------------- [~rafabene] The kitchensink-cordova and kitchensink-cordova-contacts project examples are defined as maven projects, but don't contain pom.xml and JBT can't recognize them. See https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x/kitchensink-cordova or https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x/kitchensink-cordova-contacts. You should add pom.xml or define these project examples as Eclipse projects. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114238#comment-13114238 ] Alexey Kazakov commented on JBIDE-20844: ---------------------------------------- [~snjeza] can we also warn the user if there is something wrong with the example? Add an error in the log at least? > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:06:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 1 Oct 2015 11:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20844: ---------------------------------- Component/s: (was: upstream) > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:08:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 1 Oct 2015 11:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114242#comment-13114242 ] Snjezana Peco commented on JBIDE-20844: --------------------------------------- I will try that. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:11:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 11:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20849: ----------------------------------- Assignee: Andre Dietisheim > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Final > > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:11:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 11:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20849: -------------------------------- Fix Version/s: 4.3.1.Final > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Final > > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:22:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114247#comment-13114247 ] Nick Boldt commented on JBIDE-20833: ------------------------------------ Since we're respinning today anyway, I've kicked a fresh build of central: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-central_4.3.mars/ >=45 This should pick up the B24 Final playground bits, instead of the B23 CR2 ones. To verify: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-central_4.3.mars/latest/all/repo/plugins/ should have the same version of org.jboss.tools.playground.easymport.* as in http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-playground_4.3.mars/latest/all/repo/plugins/ (1.0.0.Final-v20150925-1225-B24) Then, JBT and JBDS should pick up the newer bits when they're rebuilt today. http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.site_4.3.mars/latest/all/repo/plugins/ http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/plugins/ https://devstudio.redhat.com/9.0/snapshots/builds/devstudio.product_9.0.mars/latest/all/repo/plugins/ https://devstudio.redhat.com/9.0/snapshots/updates/core/4.3.mars/plugins/ > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Critical > Labels: respin-a > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:22:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20833: ------------------------------- Labels: respin-a (was: ) > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Critical > Labels: respin-a > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:23:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20833: ------------------------------- Priority: Blocker (was: Critical) > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:23:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20833: ------------------------------- Fix Version/s: 4.3.0.CR2 4.3.0.Final > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:23:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Thu, 1 Oct 2015 11:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19282) Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114248#comment-13114248 ] Vlado Pakan commented on JBIDE-19282: ------------------------------------- [~akazakov] you are right > Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette > --------------------------------------------------------------------------------------- > > Key: JBIDE-19282 > URL: https://issues.jboss.org/browse/JBIDE-19282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, MS Windows 7 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > # Create Hybrid Mobile project > # Add HTML page to www folder with this content > {code:html} > > > {code} > # Insert JS/CSS references from JQuery Mobile palette > # Insert Canvas tag from HTML5 palette inside tag > ERROR: These errors appear in Error log and no tag is added > {noformat} > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.661 > !MESSAGE Program Error: modelStateChanging was less than zero > !STACK 0 > java.lang.IllegalStateException: Program Error: modelStateChanging was less than zero > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.internalModelChanged(AbstractStructuredModel.java:825) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.changedModel(AbstractStructuredModel.java:361) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.changedModel(DOMModelImpl.java:171) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel$DocumentToModelNotifier.noChange(AbstractStructuredModel.java:139) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:513) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1172) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1959) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.676 > !MESSAGE Program Error: invalid structured document event > !ENTRY org.eclipse.wst.sse.core 4 2 2015-02-17 21:42:06.676 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.wst.sse.core". > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: assertion failed: > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) > at org.eclipse.jface.text.DocumentEvent.(DocumentEvent.java:62) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1911) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:24:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 11:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114249#comment-13114249 ] Martin Malina commented on JBIDE-20845: --------------------------------------- It doesn't do anything, but it turns out in my case I needed to click the List Members button in the web app to trigger the breakpoint - so eventually it worked even despite this error. But for Vlado (Fedora 22, KDE) it worked right away - no Line Number error and no need to click any button in the web app. (But as I said earlier, Pavol hit the same issue as me on Linux.) So something is odd here. But at least I was now able to verify that the source lookup but is fixed. > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:25:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Thu, 1 Oct 2015 11:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed JBIDE-20804. --------------------------------- So despite the other bug that I found (JBIDE-20845) I was eventually able to confirm this fix and see the source of the class that previously couldn't be loaded. (With the help of Vlado and Rasto.) Verified in JBDS 9.0.0.CR2 B116. > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.CR2 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:32:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 11:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19282) Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-19282: ----------------------------------- Priority: Major (was: Critical) Thanks Vlado. Changing from Critical to Major then. > Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette > --------------------------------------------------------------------------------------- > > Key: JBIDE-19282 > URL: https://issues.jboss.org/browse/JBIDE-19282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, MS Windows 7 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > # Create Hybrid Mobile project > # Add HTML page to www folder with this content > {code:html} > > > {code} > # Insert JS/CSS references from JQuery Mobile palette > # Insert Canvas tag from HTML5 palette inside tag > ERROR: These errors appear in Error log and no tag is added > {noformat} > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.661 > !MESSAGE Program Error: modelStateChanging was less than zero > !STACK 0 > java.lang.IllegalStateException: Program Error: modelStateChanging was less than zero > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.internalModelChanged(AbstractStructuredModel.java:825) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.changedModel(AbstractStructuredModel.java:361) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.changedModel(DOMModelImpl.java:171) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel$DocumentToModelNotifier.noChange(AbstractStructuredModel.java:139) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:513) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1172) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1959) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.676 > !MESSAGE Program Error: invalid structured document event > !ENTRY org.eclipse.wst.sse.core 4 2 2015-02-17 21:42:06.676 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.wst.sse.core". > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: assertion failed: > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) > at org.eclipse.jface.text.DocumentEvent.(DocumentEvent.java:62) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1911) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:34:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20736) reuse install-grinder's getAndInstallEclipse.groovy and releng-scripts when doing target platform install tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20736. ------------------------------ Resolution: Done Done and done. > reuse install-grinder's getAndInstallEclipse.groovy and releng-scripts when doing target platform install tests > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20736 > URL: https://issues.jboss.org/browse/JBIDE-20736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Instead of ugly if-then-yecch shell script and wget fetches of .sh scripts from github, we should use VERSIONED scripts from nexus. > Therefore, we should reuse install-grinder's getAndInstallEclipse.groovy and releng-scripts when doing target platform install tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:43:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 11:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-19944. --------------------------------- Resolution: Done Tested with JBDS 8.1.0.GA and 9.0.0.CR1a, everything works. No change in ide-config.properties nor respin required. Resolving. > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Final > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-product > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:46:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 1 Oct 2015 11:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-2705: -------------------------------- > update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 > ---------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 8.x, 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:46:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-2705: ----------------------------- Labels: screencast (was: ) > update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 > ---------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 8.x, 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:46:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-2705: ----------------------------- Summary: Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 (was: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715) > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 8.x, 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:46:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:46:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3282: ----------------------------- Labels: screencast (was: ) > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.0.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:48:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 11:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114261#comment-13114261 ] Fred Bricon commented on JBDS-2705: ----------------------------------- Surely we want to do JBDS 9 now, don't we? > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 8.x, 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:49:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 1 Oct 2015 11:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim reassigned JBIDE-20849: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Final > > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:52:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 1 Oct 2015 11:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3282: ----------------------------- > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.0.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:52:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 1 Oct 2015 11:52:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3282: -------------------------------- > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.0.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:52:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 11:52:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3282: ----------------------------- Component/s: documentation > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.0.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:59:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 11:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if a *.Final page already exists In-Reply-To: References: Message-ID: Fred Bricon created JBIDE-20851: ----------------------------------- Summary: Skip Final NN aggregation page if a *.Final page already exists Key: JBIDE-20851 URL: https://issues.jboss.org/browse/JBIDE-20851 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: website Reporter: Fred Bricon If a .Final NN page exists, the aggregation of all previous Alpha/Beta/CR N&N should be skipped -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:59:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 11:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if a *.Final page already exists In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20851: ----------------------------------- Assignee: Xavier Coulon > Skip Final NN aggregation page if a *.Final page already exists > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > > If a .Final NN page exists, the aggregation of all previous Alpha/Beta/CR N&N should be skipped -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if a *.Final page already exists In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114266#comment-13114266 ] Alexey Kazakov commented on JBIDE-20851: ---------------------------------------- IMO we will have more flexibility if we can have *.Final for aggregation or *.Final _replaces_ or something for replacing instead of aggregation. > Skip Final NN aggregation page if a *.Final page already exists > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > > If a .Final NN page exists, the aggregation of all previous Alpha/Beta/CR N&N should be skipped -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 12:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-2705: ----------------------------- Fix Version/s: (was: 8.x) > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 12:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-2705: ----------------------------- Summary: Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 (was: Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715) > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 12:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114268#comment-13114268 ] Nick Boldt commented on JBDS-2705: ---------------------------------- Removed 8 from this JIRA's title and set fixversion to 9.0.0.GA. > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:18:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Thu, 1 Oct 2015 12:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if a *.Final page already exists In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon updated JBIDE-20851: ---------------------------------- Fix Version/s: 4.3.0.Final > Skip Final NN aggregation page if a *.Final page already exists > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > If a .Final NN page exists, the aggregation of all previous Alpha/Beta/CR N&N should be skipped -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:29:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if a *.final.replace.adoc exists In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Summary: Skip Final NN aggregation page if a *.final.replace.adoc exists (was: Skip Final NN aggregation page if a *.Final page already exists ) > Skip Final NN aggregation page if a *.final.replace.adoc exists > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > If a .Final NN page exists, the aggregation of all previous Alpha/Beta/CR N&N should be skipped -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:32:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if a *.final.replace.adoc exists In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114275#comment-13114275 ] Alexey Kazakov commented on JBIDE-20851: ---------------------------------------- Agreed in IRC chat: 1. If *.final.replace.adoc file exists, it replaces all the N&N for a given component in the .Final N&N release note. 2. Otherwise all N&N will be aggregated (including .Final.adoc if exists). > Skip Final NN aggregation page if a *.final.replace.adoc exists > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > If a .Final NN page exists, the aggregation of all previous Alpha/Beta/CR N&N should be skipped -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:45:01 2015 From: issues at jboss.org (Rafael Benevides (JIRA)) Date: Thu, 1 Oct 2015 12:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114280#comment-13114280 ] Rafael Benevides commented on JBIDE-20844: ------------------------------------------ Hi [~snjeza]. Actually they are marked in the non-maven profile: https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.7.x/pom.xml#L191-L202 > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:48:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if a *.final.replace.adoc exists In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Description: Add an attribute check i.e. "Include-previous: " If true (default value) then skip the final aggregation and use this only doc as a final N&N. If false then aggregate all N&N docs (including this one). was:If a .Final NN page exists, the aggregation of all previous Alpha/Beta/CR N&N should be skipped > Skip Final NN aggregation page if a *.final.replace.adoc exists > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If true (default value) then skip the final aggregation and use this only doc as a final N&N. > If false then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "Include-previous: true" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Summary: Skip Final NN aggregation page if "Include-previous: true" (was: Skip Final NN aggregation page if a *.final.replace.adoc exists ) > Skip Final NN aggregation page if "Include-previous: true" > ---------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If true (default value) then skip the final aggregation and use this only doc as a final N&N. > If false then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "Include-previous: true" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Comment: was deleted (was: Agreed in IRC chat: 1. If *.final.replace.adoc file exists, it replaces all the N&N for a given component in the .Final N&N release note. 2. Otherwise all N&N will be aggregated (including .Final.adoc if exists).) > Skip Final NN aggregation page if "Include-previous: true" > ---------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If true (default value) then skip the final aggregation and use this only doc as a final N&N. > If false then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:50:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "Include-previous: true" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114284#comment-13114284 ] Alexey Kazakov commented on JBIDE-20851: ---------------------------------------- Updated summary and description after some discussion with Xavier, Fred and Max. > Skip Final NN aggregation page if "Include-previous: true" > ---------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If true (default value) then skip the final aggregation and use this only doc as a final N&N. > If false then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:54:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "Include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Summary: Skip Final NN aggregation page if "Include-previous: false" (was: Skip Final NN aggregation page if "Include-previous: true") > Skip Final NN aggregation page if "Include-previous: false" > ----------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If true (default value) then skip the final aggregation and use this only doc as a final N&N. > If false then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:54:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "Include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Description: Add an attribute check i.e. "Include-previous: " If false then skip the final aggregation and use this only doc as a final N&N. If true (default value) then aggregate all N&N docs (including this one). was: Add an attribute check i.e. "Include-previous: " If true (default value) then skip the final aggregation and use this only doc as a final N&N. If false then aggregate all N&N docs (including this one). > Skip Final NN aggregation page if "Include-previous: false" > ----------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 12:58:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 12:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "Include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114285#comment-13114285 ] Fred Bricon commented on JBIDE-20851: ------------------------------------- Does the build know how to order aggregated files? Will the content of .Final always be on top (or at the bottom) of each aggregated NN? > Skip Final NN aggregation page if "Include-previous: false" > ----------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "Include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114287#comment-13114287 ] Alexey Kazakov commented on JBIDE-20851: ---------------------------------------- It was confirmed by Xavier, that the .Final is always at the bottom. But if we have one more directive which would set the order for the .Final doc, it would be useful. > Skip Final NN aggregation page if "Include-previous: false" > ----------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:29:00 2015 From: issues at jboss.org (Dmitry Bocharov (JIRA)) Date: Thu, 1 Oct 2015 13:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114297#comment-13114297 ] Dmitry Bocharov commented on JBIDE-20801: ----------------------------------------- The same was detected for New Hibernate reverse engineering file. After adding _sc.pack()_ in the end of _createControl _method controls appeared. May i commit to the current task or it is better to create another one? > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20852) Create New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20852: -------------------------------------- Summary: Create New and Noteworthy for 4.3.0.Final Key: JBIDE-20852 URL: https://issues.jboss.org/browse/JBIDE-20852 Project: Tools (JBoss Tools) Issue Type: Task Components: website Reporter: Alexey Kazakov Priority: Blocker Fix For: 4.3.0.Final This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20853) jst/jsf New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20853: -------------------------------------- Summary: jst/jsf New and Noteworthy for 4.3.0.Final Key: JBIDE-20853 URL: https://issues.jboss.org/browse/JBIDE-20853 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html-source-editing, jsf Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22jsf%22%2C%22jsp%2Fjsf%2Fxml%2Fhtml-source-editing%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If jst/jsf is not listed here check if there are issues that should be added and add them. Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20854) Arquillian New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20854: -------------------------------------- Summary: Arquillian New and Noteworthy for 4.3.0.Final Key: JBIDE-20854 URL: https://issues.jboss.org/browse/JBIDE-20854 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: arquillian Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22arquillian%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Arquillian is not listed here check if there are issues that should be added and add them. Document the ones relevant for Arquillian by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20855) Forge New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20855: -------------------------------------- Summary: Forge New and Noteworthy for 4.3.0.Final Key: JBIDE-20855 URL: https://issues.jboss.org/browse/JBIDE-20855 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: forge Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22forge%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Forge is not listed here check if there are issues that should be added and add them. Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20856) Visual Editor New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20856: -------------------------------------- Summary: Visual Editor New and Noteworthy for 4.3.0.Final Key: JBIDE-20856 URL: https://issues.jboss.org/browse/JBIDE-20856 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: visual-page-editor-templates, visual-page-editor-core Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22visual-page-editor-templates%22%2C%22visual-page-editor-core%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Visual Editor is not listed here check if there are issues that should be added and add them. Document the ones relevant for Visual Editor by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20857) Aerogear New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20857: -------------------------------------- Summary: Aerogear New and Noteworthy for 4.3.0.Final Key: JBIDE-20857 URL: https://issues.jboss.org/browse/JBIDE-20857 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22aerogear-hybrid%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Aerogear is not listed here check if there are issues that should be added and add them. Document the ones relevant for Aerogear by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20858) Maven New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20858: -------------------------------------- Summary: Maven New and Noteworthy for 4.3.0.Final Key: JBIDE-20858 URL: https://issues.jboss.org/browse/JBIDE-20858 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22maven%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Maven is not listed here check if there are issues that should be added and add them. Document the ones relevant for Maven by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20859) Project Examples New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20859: -------------------------------------- Summary: Project Examples New and Noteworthy for 4.3.0.Final Key: JBIDE-20859 URL: https://issues.jboss.org/browse/JBIDE-20859 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: project-examples Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22project-examples%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Project Examples is not listed here check if there are issues that should be added and add them. Document the ones relevant for Project Examples by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20860) OpenShift New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20860: -------------------------------------- Summary: OpenShift New and Noteworthy for 4.3.0.Final Key: JBIDE-20860 URL: https://issues.jboss.org/browse/JBIDE-20860 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22openshift%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If OpenShift is not listed here check if there are issues that should be added and add them. Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20862) Live Reload New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20862: -------------------------------------- Summary: Live Reload New and Noteworthy for 4.3.0.Final Key: JBIDE-20862 URL: https://issues.jboss.org/browse/JBIDE-20862 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: livereload Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22livereload%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Live Reload is not listed here check if there are issues that should be added and add them. Document the ones relevant for Live Reload by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20861) Easy import New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20861: -------------------------------------- Summary: Easy import New and Noteworthy for 4.3.0.Final Key: JBIDE-20861 URL: https://issues.jboss.org/browse/JBIDE-20861 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: easymport Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22easymport%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Easy import is not listed here check if there are issues that should be added and add them. Document the ones relevant for Easy import by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20863) hibernate New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20863: -------------------------------------- Summary: hibernate New and Noteworthy for 4.3.0.Final Key: JBIDE-20863 URL: https://issues.jboss.org/browse/JBIDE-20863 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: hibernate Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22hibernate%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If hibernate is not listed here check if there are issues that should be added and add them. Document the ones relevant for hibernate by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20865) javascript New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20865: -------------------------------------- Summary: javascript New and Noteworthy for 4.3.0.Final Key: JBIDE-20865 URL: https://issues.jboss.org/browse/JBIDE-20865 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: javascript-bower, javascript Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22javascript-bower%22%2C%22javascript%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If javascript is not listed here check if there are issues that should be added and add them. Document the ones relevant for javascript by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20864) Freemarker New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20864: -------------------------------------- Summary: Freemarker New and Noteworthy for 4.3.0.Final Key: JBIDE-20864 URL: https://issues.jboss.org/browse/JBIDE-20864 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: freemarker Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22freemarker%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Freemarker is not listed here check if there are issues that should be added and add them. Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20866) Batch New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20866: -------------------------------------- Summary: Batch New and Noteworthy for 4.3.0.Final Key: JBIDE-20866 URL: https://issues.jboss.org/browse/JBIDE-20866 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: batch Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22batch%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Batch is not listed here check if there are issues that should be added and add them. Document the ones relevant for Batch by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20867) BrowserSim New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20867: -------------------------------------- Summary: BrowserSim New and Noteworthy for 4.3.0.Final Key: JBIDE-20867 URL: https://issues.jboss.org/browse/JBIDE-20867 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: browsersim Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22browsersim%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If BrowserSim is not listed here check if there are issues that should be added and add them. Document the ones relevant for BrowserSim by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20868) Usage Analytics New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20868: -------------------------------------- Summary: Usage Analytics New and Noteworthy for 4.3.0.Final Key: JBIDE-20868 URL: https://issues.jboss.org/browse/JBIDE-20868 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: usage Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22usage%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Usage Analytics is not listed here check if there are issues that should be added and add them. Document the ones relevant for Usage Analytics by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20870) JBoss Central New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20870: -------------------------------------- Summary: JBoss Central New and Noteworthy for 4.3.0.Final Key: JBIDE-20870 URL: https://issues.jboss.org/browse/JBIDE-20870 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: central Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22central%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If JBoss Central is not listed here check if there are issues that should be added and add them. Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:40:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:40:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20869) Docker New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20869: -------------------------------------- Summary: Docker New and Noteworthy for 4.3.0.Final Key: JBIDE-20869 URL: https://issues.jboss.org/browse/JBIDE-20869 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: docker Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22docker%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Docker is not listed here check if there are issues that should be added and add them. Document the ones relevant for Docker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20871) Core/General New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20871: -------------------------------------- Summary: Core/General New and Noteworthy for 4.3.0.Final Key: JBIDE-20871 URL: https://issues.jboss.org/browse/JBIDE-20871 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: common/jst/core Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22common%2Fjst%2Fcore%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Core/General is not listed here check if there are issues that should be added and add them. Document the ones relevant for Core/General by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20872) Webservices and Rest New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20872: -------------------------------------- Summary: Webservices and Rest New and Noteworthy for 4.3.0.Final Key: JBIDE-20872 URL: https://issues.jboss.org/browse/JBIDE-20872 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: webservices Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22webservices%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Webservices and Rest is not listed here check if there are issues that should be added and add them. Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20873) CDI New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20873: -------------------------------------- Summary: CDI New and Noteworthy for 4.3.0.Final Key: JBIDE-20873 URL: https://issues.jboss.org/browse/JBIDE-20873 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22cdi%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If CDI is not listed here check if there are issues that should be added and add them. Document the ones relevant for CDI by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20874) server New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20874: -------------------------------------- Summary: server New and Noteworthy for 4.3.0.Final Key: JBIDE-20874 URL: https://issues.jboss.org/browse/JBIDE-20874 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server, jmx, archives Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22jmx%22%2C%22archives%22%2C%22server%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If server is not listed here check if there are issues that should be added and add them. Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20875) Seam New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20875: -------------------------------------- Summary: Seam New and Noteworthy for 4.3.0.Final Key: JBIDE-20875 URL: https://issues.jboss.org/browse/JBIDE-20875 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: seam2 Reporter: Alexey Kazakov Priority: Critical This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22seam2%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. If Seam is not listed here check if there are issues that should be added and add them. Document the ones relevant for Seam by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:43:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20876) Create New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20876: -------------------------------------- Summary: Create New and Noteworthy for 4.3.0.Final Key: JBIDE-20876 URL: https://issues.jboss.org/browse/JBIDE-20876 Project: Tools (JBoss Tools) Issue Type: Task Components: website Reporter: Alexey Kazakov Priority: Blocker Fix For: 4.3.0.Final This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:43:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20877) jst/jsf New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20877: -------------------------------------- Summary: jst/jsf New and Noteworthy for 4.3.0.Final Key: JBIDE-20877 URL: https://issues.jboss.org/browse/JBIDE-20877 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html-source-editing, jsf Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22jsf%22%2C%22jsp%2Fjsf%2Fxml%2Fhtml-source-editing%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20878) Arquillian New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20878: -------------------------------------- Summary: Arquillian New and Noteworthy for 4.3.0.Final Key: JBIDE-20878 URL: https://issues.jboss.org/browse/JBIDE-20878 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: arquillian Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22arquillian%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20879) Forge New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20879: -------------------------------------- Summary: Forge New and Noteworthy for 4.3.0.Final Key: JBIDE-20879 URL: https://issues.jboss.org/browse/JBIDE-20879 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: forge Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22forge%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20880) Visual Editor New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20880: -------------------------------------- Summary: Visual Editor New and Noteworthy for 4.3.0.Final Key: JBIDE-20880 URL: https://issues.jboss.org/browse/JBIDE-20880 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: visual-page-editor-templates, visual-page-editor-core Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22visual-page-editor-templates%22%2C%22visual-page-editor-core%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20882) Maven New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20882: -------------------------------------- Summary: Maven New and Noteworthy for 4.3.0.Final Key: JBIDE-20882 URL: https://issues.jboss.org/browse/JBIDE-20882 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22maven%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20881) Aerogear New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20881: -------------------------------------- Summary: Aerogear New and Noteworthy for 4.3.0.Final Key: JBIDE-20881 URL: https://issues.jboss.org/browse/JBIDE-20881 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22aerogear-hybrid%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20885) Easy import New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20885: -------------------------------------- Summary: Easy import New and Noteworthy for 4.3.0.Final Key: JBIDE-20885 URL: https://issues.jboss.org/browse/JBIDE-20885 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: easymport Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22easymport%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20883) Project Examples New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20883: -------------------------------------- Summary: Project Examples New and Noteworthy for 4.3.0.Final Key: JBIDE-20883 URL: https://issues.jboss.org/browse/JBIDE-20883 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: project-examples Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22project-examples%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20886) Live Reload New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20886: -------------------------------------- Summary: Live Reload New and Noteworthy for 4.3.0.Final Key: JBIDE-20886 URL: https://issues.jboss.org/browse/JBIDE-20886 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: livereload Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22livereload%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20887) hibernate New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20887: -------------------------------------- Summary: hibernate New and Noteworthy for 4.3.0.Final Key: JBIDE-20887 URL: https://issues.jboss.org/browse/JBIDE-20887 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: hibernate Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22hibernate%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20888) Freemarker New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20888: -------------------------------------- Summary: Freemarker New and Noteworthy for 4.3.0.Final Key: JBIDE-20888 URL: https://issues.jboss.org/browse/JBIDE-20888 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: freemarker Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22freemarker%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20889) javascript New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20889: -------------------------------------- Summary: javascript New and Noteworthy for 4.3.0.Final Key: JBIDE-20889 URL: https://issues.jboss.org/browse/JBIDE-20889 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: javascript-bower, javascript Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22javascript-bower%22%2C%22javascript%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20890) Batch New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20890: -------------------------------------- Summary: Batch New and Noteworthy for 4.3.0.Final Key: JBIDE-20890 URL: https://issues.jboss.org/browse/JBIDE-20890 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: batch Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22batch%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20891) BrowserSim New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20891: -------------------------------------- Summary: BrowserSim New and Noteworthy for 4.3.0.Final Key: JBIDE-20891 URL: https://issues.jboss.org/browse/JBIDE-20891 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: browsersim Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22browsersim%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20893) Docker New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20893: -------------------------------------- Summary: Docker New and Noteworthy for 4.3.0.Final Key: JBIDE-20893 URL: https://issues.jboss.org/browse/JBIDE-20893 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: docker Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22docker%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20892) Usage Analytics New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20892: -------------------------------------- Summary: Usage Analytics New and Noteworthy for 4.3.0.Final Key: JBIDE-20892 URL: https://issues.jboss.org/browse/JBIDE-20892 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: usage Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22usage%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20894) JBoss Central New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20894: -------------------------------------- Summary: JBoss Central New and Noteworthy for 4.3.0.Final Key: JBIDE-20894 URL: https://issues.jboss.org/browse/JBIDE-20894 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: central Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22central%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20895) Core/General New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20895: -------------------------------------- Summary: Core/General New and Noteworthy for 4.3.0.Final Key: JBIDE-20895 URL: https://issues.jboss.org/browse/JBIDE-20895 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: common/jst/core Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22common%2Fjst%2Fcore%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20896) Webservices and Rest New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20896: -------------------------------------- Summary: Webservices and Rest New and Noteworthy for 4.3.0.Final Key: JBIDE-20896 URL: https://issues.jboss.org/browse/JBIDE-20896 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: webservices Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22webservices%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20897) CDI New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20897: -------------------------------------- Summary: CDI New and Noteworthy for 4.3.0.Final Key: JBIDE-20897 URL: https://issues.jboss.org/browse/JBIDE-20897 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22cdi%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20898) server New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20898: -------------------------------------- Summary: server New and Noteworthy for 4.3.0.Final Key: JBIDE-20898 URL: https://issues.jboss.org/browse/JBIDE-20898 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server, jmx, archives Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22jmx%22%2C%22archives%22%2C%22server%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20884: -------------------------------------- Summary: OpenShift New and Noteworthy for 4.3.0.Final Key: JBIDE-20884 URL: https://issues.jboss.org/browse/JBIDE-20884 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22openshift%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:45:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20899) Seam New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20899: -------------------------------------- Summary: Seam New and Noteworthy for 4.3.0.Final Key: JBIDE-20899 URL: https://issues.jboss.org/browse/JBIDE-20899 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: seam2 Reporter: Alexey Kazakov Priority: Critical If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22seam2%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:45:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 13:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20876) Create New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20876: -------------------------------------- Assignee: Alexey Kazakov > Create New and Noteworthy for 4.3.0.Final > ----------------------------------------- > > Key: JBIDE-20876 > URL: https://issues.jboss.org/browse/JBIDE-20876 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.3.0.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:47:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 1 Oct 2015 13:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20888) Freemarker New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin closed JBIDE-20888. --------------------------------- Resolution: Rejected > Freemarker New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20888 > URL: https://issues.jboss.org/browse/JBIDE-20888 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22freemarker%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 13:48:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 13:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBIDE-20833. -------------------------------- Resolution: Done Rebuilt. Resolving. > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20895) Core/General New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20895. ---------------------------------- Resolution: Rejected > Core/General New and Noteworthy for 4.3.0.Final > ----------------------------------------------- > > Key: JBIDE-20895 > URL: https://issues.jboss.org/browse/JBIDE-20895 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22common%2Fjst%2Fcore%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20895) Core/General New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20895: -------------------------------------- Assignee: Alexey Kazakov > Core/General New and Noteworthy for 4.3.0.Final > ----------------------------------------------- > > Key: JBIDE-20895 > URL: https://issues.jboss.org/browse/JBIDE-20895 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22common%2Fjst%2Fcore%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20899) Seam New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20899. ---------------------------------- Assignee: Alexey Kazakov Resolution: Rejected > Seam New and Noteworthy for 4.3.0.Final > --------------------------------------- > > Key: JBIDE-20899 > URL: https://issues.jboss.org/browse/JBIDE-20899 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: seam2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22seam2%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:05:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20897) CDI New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20897. ---------------------------------- Assignee: Alexey Kazakov Resolution: Rejected > CDI New and Noteworthy for 4.3.0.Final > -------------------------------------- > > Key: JBIDE-20897 > URL: https://issues.jboss.org/browse/JBIDE-20897 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22cdi%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:09:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 14:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20848: ---------------------------------- Assignee: Nick Boldt (was: Mickael Istria) Resolution: Done Jobs updated: https://github.com/jbdevstudio/jbdevstudio-ci/commit/f5b5b51f5c0c50d8defa0bebb1d5dd36a90814ae (4.3.x) https://github.com/jbdevstudio/jbdevstudio-ci/commit/b753c857eb2503a1e6542d453da01242e704897d (master) Kicked: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-build-sites.aggregate.site_4.3.mars/ >=126 Need a blue build and to see the correct version of org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip in the log: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-build-sites.aggregate.site_4.3.mars/lastBuild/consoleText > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:11:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20877) jst/jsf New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20877: -------------------------------------- Assignee: Alexey Kazakov > jst/jsf New and Noteworthy for 4.3.0.Final > ------------------------------------------ > > Key: JBIDE-20877 > URL: https://issues.jboss.org/browse/JBIDE-20877 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22jsf%22%2C%22jsp%2Fjsf%2Fxml%2Fhtml-source-editing%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:12:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 1 Oct 2015 14:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20885) Easy import New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114307#comment-13114307 ] Mickael Istria commented on JBIDE-20885: ---------------------------------------- [~akazakov] There is no change for CR/FInal, but as I wrote something to add it to Beta2: https://github.com/jbosstools/jbosstools-website/pull/498 > Easy import New and Noteworthy for 4.3.0.Final > ---------------------------------------------- > > Key: JBIDE-20885 > URL: https://issues.jboss.org/browse/JBIDE-20885 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: easymport > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22easymport%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:16:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20879) Forge New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20879: -------------------------------------- Assignee: George Gastaldi cc: [~koen.aers] > Forge New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20879 > URL: https://issues.jboss.org/browse/JBIDE-20879 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22forge%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:34:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20885) Easy import New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20885. ------------------------------------ Assignee: Mickael Istria Resolution: Done I have pushed the Beta2 N&N to master and production. Resolving this issue too. Thanks! > Easy import New and Noteworthy for 4.3.0.Final > ---------------------------------------------- > > Key: JBIDE-20885 > URL: https://issues.jboss.org/browse/JBIDE-20885 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: easymport > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22easymport%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20890) Batch New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20890: -------------------------------------- Assignee: Alexey Kazakov > Batch New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20890 > URL: https://issues.jboss.org/browse/JBIDE-20890 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22batch%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20898) server New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20898: -------------------------------------- Assignee: Alexey Kazakov > server New and Noteworthy for 4.3.0.Final > ----------------------------------------- > > Key: JBIDE-20898 > URL: https://issues.jboss.org/browse/JBIDE-20898 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22jmx%22%2C%22archives%22%2C%22server%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:50:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 14:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for releng-scripts? In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20900: ---------------------------------- Summary: why do we need both zip and tar.gz for releng-scripts? Key: JBIDE-20900 URL: https://issues.jboss.org/browse/JBIDE-20900 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 4.4.0.Alpha1 When publishing, we use this: {code} [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack {code} But there's also this: {code} [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz (25 KB at 99.3 KB/sec) [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes "" [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code} So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:50:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 14:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for releng-scripts? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20900: ------------------------------- Description: When publishing, we use this: {code} [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack {code} But there's also this: {code} [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz (25 KB at 99.3 KB/sec) [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes "" [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code} So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip. was: When publishing, we use this: {code} [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack {code} But there's also this: {code} [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz (25 KB at 99.3 KB/sec) [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes "" [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code} So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip. > why do we need both zip and tar.gz for releng-scripts? > ------------------------------------------------------ > > Key: JBIDE-20900 > URL: https://issues.jboss.org/browse/JBIDE-20900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > When publishing, we use this: > {code} > [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final > -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" > -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true > -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip > -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources > -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack > {code} > But there's also this: > {code} > [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz > [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz > [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz > [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz (25 KB at 99.3 KB/sec) > [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes "" > [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code} > So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:51:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 14:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20892) Usage Analytics New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20892. ---------------------------------- Assignee: Alexey Kazakov Resolution: Rejected > Usage Analytics New and Noteworthy for 4.3.0.Final > -------------------------------------------------- > > Key: JBIDE-20892 > URL: https://issues.jboss.org/browse/JBIDE-20892 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22usage%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:51:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 14:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20900: ------------------------------- Summary: why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ? (was: why do we need both zip and tar.gz for releng-scripts?) > why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20900 > URL: https://issues.jboss.org/browse/JBIDE-20900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > When publishing, we use this: > {code} > [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final > -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" > -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true > -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip > -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources > -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack > {code} > But there's also this: > {code} > [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz > [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz > [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz > [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz (25 KB at 99.3 KB/sec) > [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes "" > [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code} > So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 14:56:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 14:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114313#comment-13114313 ] Nick Boldt commented on JBDS-3532: ---------------------------------- PR for review: https://github.com/jbdevstudio/jbdevstudio-product/pull/343 > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:20:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 15:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114317#comment-13114317 ] Nick Boldt commented on JBDS-3532: ---------------------------------- {quote} (2015-10-01 14:58:02) nickboldt: akazakov: it built great in master branch for me; verified contents but haven't tried install yet (2015-10-01 14:59:28) akazakov: nickboldt, can you try to install it now? If everything works then +1 from me (2015-10-01 15:00:53) nickboldt: akazakov: yes, in progress (2015-10-01 15:01:15) nickboldt: akazakov: first, a BYOE feature install ... (2015-10-01 15:04:19) nickboldt: akazakov: dgolovin: install of master branch's new update site zip (with the above PR) worked here for BYOE feature (2015-10-01 15:04:32) nickboldt: now going to try installing the Branded Product feature (2015-10-01 15:04:42) nickboldt: (which isn't really supported but curious) (2015-10-01 15:05:12) nickboldt: meanwhile building the same PR in 4.3.x branch to verify it works there too (2015-10-01 15:07:09) nickboldt: site built but installer part of the build still going. starting JBDS 9 install from new update site zip test... (2015-10-01 15:09:48) nickboldt: JBDS 10 install test worked. (Remediation presented to support updating from EPP to JBDS product, but that's 100% expected and necessary) (2015-10-01 15:11:36) nickboldt: ...and I ran out of disk space. :( (2015-10-01 15:13:40) akazakov: nickboldt, +1 if all tests passed. Merge into 4.3.x. (2015-10-01 15:16:43) nickboldt: install test passed for JBDS 9 BYOE and Product features into Mars.1.RC3 JEE (2015-10-01 15:17:06) nickboldt: going to try to complete the build of the installer (freed up some disk) {quote} I've merged the PR while I re-run the part of the full JBDS build that failed due to lack of disk (just the product/installer/pom.xml module, which is unaffected by this). > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:30:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 15:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20848) Release publish scripts and use them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20848. ------------------------------ Closing. Found another related issue in JBIDE-20900 but that's not urgent. > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:33:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 15:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114322#comment-13114322 ] Nick Boldt commented on JBDS-3532: ---------------------------------- {quote} 2015-10-01 15:29:24) dgolovin: nickboldt: if installer build is fine, then installer should be fine, because build runs automated installation from built installer jar to verify it works. (2015-10-01 15:30:00) nickboldt: dgolovin: yep, that part passed once I had enough disk space free :D {quote} ---- Comparing filesizes from my local build to the sizes in CR1 release: {code:title=http://www.jboss.org/products/devstudio/download/} Installer With EAP (633mb) Stand-alone Installer (489mb) Update Site Zip (514mb) Source Zip (223mb) {code} {code:title=locally built} Installer With EAP (633mb) Stand-alone Installer (489mb) Update Site Zip (514mb) Source Zip (223mb) {code} So... win! Next: disabling the stuff in the _master job we no longer need & kicking that job anew: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_master/ >= 4000 ! (Yes, with this fix we'll be #overFourThousand. Onward to 9000!) > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:34:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 1 Oct 2015 15:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3532: ----------------------------- > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:34:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 15:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3532: ----------------------------- Status: New (was: New) Target Release: 9.0.0.GA > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:34:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 15:34:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3532: ----------------------------- > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:34:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 1 Oct 2015 15:34:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3532: ----------------------------- > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:34:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 1 Oct 2015 15:34:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3532: -------------------------------- > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:34:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 15:34:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3532: ----------------------------- > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 15:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 15:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBDS-3532. ------------------------------ Resolution: Done Resolving. QE can verify using whatever method they normally use to ensure the new update site zip works and contains the same IU versions as the installer starting from these builds: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_9.0.mars/ >=123 (which should be the build number for CR2a) --> https://devstudio.redhat.com/9.0/snapshots/builds/devstudio.product_9.0.mars/latest/all/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_master/ >=4000 -> https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.product_master/latest/all/ > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 16:14:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 1 Oct 2015 16:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20878) Arquillian New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco reassigned JBIDE-20878: ------------------------------------- Assignee: Snjezana Peco > Arquillian New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20878 > URL: https://issues.jboss.org/browse/JBIDE-20878 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Alexey Kazakov > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22arquillian%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 16:15:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 1 Oct 2015 16:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20878) Arquillian New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco resolved JBIDE-20878. ----------------------------------- Resolution: Done No changes for N&N. > Arquillian New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20878 > URL: https://issues.jboss.org/browse/JBIDE-20878 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Alexey Kazakov > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22arquillian%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 16:24:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 16:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20901) JBDS update site builds produces update site zip TWICE In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20901: ---------------------------------- Summary: JBDS update site builds produces update site zip TWICE Key: JBIDE-20901 URL: https://issues.jboss.org/browse/JBIDE-20901 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt JBDS build creates the update site zip TWICE: {code} [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip [INFO] [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 16:25:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 16:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20901) JBDS update site builds produces update site zip TWICE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20901: ------------------------------- Fix Version/s: 4.4.0.Alpha1 > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBIDE-20901 > URL: https://issues.jboss.org/browse/JBIDE-20901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 16:25:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 1 Oct 2015 16:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20901) JBDS update site builds produces update site zip TWICE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20901: ---------------------------------- Assignee: Nick Boldt > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBIDE-20901 > URL: https://issues.jboss.org/browse/JBIDE-20901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 18:58:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 1 Oct 2015 18:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20879) Forge New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi closed JBIDE-20879. ----------------------------------- Resolution: Done > Forge New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20879 > URL: https://issues.jboss.org/browse/JBIDE-20879 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22forge%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 18:58:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 1 Oct 2015 18:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20879) Forge New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi closed JBIDE-20879. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20879 > URL: https://issues.jboss.org/browse/JBIDE-20879 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22forge%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 19:33:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 19:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Summary: Skip Final NN aggregation page if include-previous: false" (was: Skip Final NN aggregation page if "Include-previous: false") > Skip Final NN aggregation page if include-previous: false" > ---------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "Include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 19:33:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 19:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Description: Add an attribute check i.e. "include-previous: " If false then skip the final aggregation and use this only doc as a final N&N. If true (default value) then aggregate all N&N docs (including this one). was: Add an attribute check i.e. "Include-previous: " If false then skip the final aggregation and use this only doc as a final N&N. If true (default value) then aggregate all N&N docs (including this one). > Skip Final NN aggregation page if include-previous: false" > ---------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 19:35:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 19:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20851: ----------------------------------- Summary: Skip Final NN aggregation page if "include-previous: false" (was: Skip Final NN aggregation page if include-previous: false") > Skip Final NN aggregation page if "include-previous: false" > ----------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 20:00:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 1 Oct 2015 20:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114352#comment-13114352 ] Alexey Kazakov commented on JBIDE-20851: ---------------------------------------- Just checked with .Final for server N&N. The order I got: CR1 Final Alpha1 Beta1 Beta2 It's a weird order :) Looks like another issue. > Skip Final NN aggregation page if "include-previous: false" > ----------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 23:28:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 23:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20894) JBoss Central New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon closed JBIDE-20894. ------------------------------- Resolution: Rejected Automatic aggregation is good enough for Central NNs. Rejecting. > JBoss Central New and Noteworthy for 4.3.0.Final > ------------------------------------------------ > > Key: JBIDE-20894 > URL: https://issues.jboss.org/browse/JBIDE-20894 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22central%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 23:37:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 23:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20883) Project Examples New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20883: ----------------------------------- Assignee: Fred Bricon > Project Examples New and Noteworthy for 4.3.0.Final > --------------------------------------------------- > > Key: JBIDE-20883 > URL: https://issues.jboss.org/browse/JBIDE-20883 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22project-examples%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 23:38:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 23:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20883) Project Examples New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-20883. --------------------------------- Resolution: Done Removed irrelevant NN bit from 4.3.0.Final > Project Examples New and Noteworthy for 4.3.0.Final > --------------------------------------------------- > > Key: JBIDE-20883 > URL: https://issues.jboss.org/browse/JBIDE-20883 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22project-examples%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 23:53:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 23:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20882) Maven New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20882: ----------------------------------- Assignee: Fred Bricon > Maven New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20882 > URL: https://issues.jboss.org/browse/JBIDE-20882 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22maven%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 23:54:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 1 Oct 2015 23:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20882) Maven New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-20882. --------------------------------- Resolution: Done Added custom 4.3.0.Final NN for Maven. > Maven New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20882 > URL: https://issues.jboss.org/browse/JBIDE-20882 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22maven%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 00:05:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 00:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20895) Core/General New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20895: ----------------------------------- Resolution: (was: Rejected) Assignee: Fred Bricon (was: Alexey Kazakov) Reopened as General section has a section on Alpha1 release > Core/General New and Noteworthy for 4.3.0.Final > ----------------------------------------------- > > Key: JBIDE-20895 > URL: https://issues.jboss.org/browse/JBIDE-20895 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22common%2Fjst%2Fcore%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 00:10:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 00:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20895) Core/General New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-20895. --------------------------------- Resolution: Done Fixed in master > Core/General New and Noteworthy for 4.3.0.Final > ----------------------------------------------- > > Key: JBIDE-20895 > URL: https://issues.jboss.org/browse/JBIDE-20895 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22common%2Fjst%2Fcore%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 00:27:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Fri, 2 Oct 2015 00:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20879) Forge New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114371#comment-13114371 ] George Gastaldi commented on JBIDE-20879: ----------------------------------------- Thanks for reminding me. Totally missed that :) Here you go: https://github.com/jbosstools/jbosstools-website/pull/503 > Forge New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20879 > URL: https://issues.jboss.org/browse/JBIDE-20879 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22forge%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:08:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Fri, 2 Oct 2015 02:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-686: ------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT (was: 12-Oct >> 25-Oct 2015-JBDS/JBT) > JBDS 9 GA: Release Notes > ------------------------ > > Key: TOOLSDOC-686 > URL: https://issues.jboss.org/browse/TOOLSDOC-686 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:08:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Fri, 2 Oct 2015 02:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: Misha Ali created TOOLSDOC-686: ---------------------------------- Summary: JBDS 9 GA: Release Notes Key: TOOLSDOC-686 URL: https://issues.jboss.org/browse/TOOLSDOC-686 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:14:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Fri, 2 Oct 2015 02:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-686: ------------------------------- Affects Version/s: 4.3.0.Final > JBDS 9 GA: Release Notes > ------------------------ > > Key: TOOLSDOC-686 > URL: https://issues.jboss.org/browse/TOOLSDOC-686 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:14:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Fri, 2 Oct 2015 02:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-686: ------------------------------- Component/s: Release Notes > JBDS 9 GA: Release Notes > ------------------------ > > Key: TOOLSDOC-686 > URL: https://issues.jboss.org/browse/TOOLSDOC-686 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:14:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Fri, 2 Oct 2015 02:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-686: ------------------------------- Description: Update CR1 release notes for GA. > JBDS 9 GA: Release Notes > ------------------------ > > Key: TOOLSDOC-686 > URL: https://issues.jboss.org/browse/TOOLSDOC-686 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > > Update CR1 release notes for GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:15:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Fri, 2 Oct 2015 02:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes In-Reply-To: References: Message-ID: Misha Ali created TOOLSDOC-687: ---------------------------------- Summary: Review JBDS 9 GA Release Notes Key: TOOLSDOC-687 URL: https://issues.jboss.org/browse/TOOLSDOC-687 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Reporter: Misha Ali Assignee: Martin Malina Please review here: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:28:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Fri, 2 Oct 2015 02:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114377#comment-13114377 ] Misha Ali commented on TOOLSDOC-683: ------------------------------------ Thanks, guys. I have a draft here if anyone wants to have a look at the reviewed version: https://access.redhat.com/node/427493/draft (scroll down to "Frameworks") In case someone doesn't have customer portal credentials yet: For iOS: 3.5.0, 3.6.0, 3.6.1, 3.6.3, 3.7.0, 3.8.0, 3.9.0 For Cordova-Android: 3.5.0, 3.5.1, 3.6.0, 3.6.1, 3.6.3, 3.6.4, 3.7.0, 3.7.1, 3.7.2, 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.1.1 I'll wait to publish this until QE finished verifying and we can finalize the list of versions. > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 02:42:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Fri, 2 Oct 2015 02:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114379#comment-13114379 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- > Spoke to Jan and he isn't sure if they will release GA or CR2 next week. [~mhusnain], wherever necessary, wdyt should the version of JBDS be in the Install guide, CR2 or GA? > I have taken the SS to be included in the Install JBDS BYOE Online chapter with "CR1". I will not be able to take a CR2/GA SS until the product is released next week and is available to be installed through the eclipse marketplace (right now since it isn't released it is not available through marketplace) > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 03:09:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Fri, 2 Oct 2015 03:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114384#comment-13114384 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- > Commented the Beta Release chapter out > Added an entry for changes done for GA in Rev History (44509) > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 03:39:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 03:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114393#comment-13114393 ] Andre Dietisheim commented on JBIDE-20884: ------------------------------------------ [~fbricon] any chance you'd do this since you're the best informed in what happened and what among it is worth noting? > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22openshift%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 03:45:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 03:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20847) Only "retrieve" and "sign up here" link inside styled text should be accessible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20847: ------------------------------------- Fix Version/s: 4.3.1.Final > Only "retrieve" and "sign up here" link inside styled text should be accessible > ------------------------------------------------------------------------------- > > Key: JBIDE-20847 > URL: https://issues.jboss.org/browse/JBIDE-20847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Labels: connection_wizard > Fix For: 4.3.1.Final > > > In New Connection dialog are 2 styled texts with links. > First one is for OpenShift 2 server selection on top saying "If you do not have an account on OpenShift, please +sign up here+." > Second one is for OpenShift 3 while OAuth authentication protocol is selected "Enter a token or +retrieve+ a new one." > Issue is that both are clickable whole, not just the underlined parts. > Issue is also differences while mouse cursor is moving over them. Second one, about a token, has hand cursor while mouse is over the text. First one has typical cursor for text. The cursor could be: > - for clickable part hand cursor > - for nonclickable part arrow cursor > Example of nice working text with link is link for OpenShift 3 server on top of wizard "New to OpenShift 3? Explore the +getting started documentation+." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 04:58:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Fri, 2 Oct 2015 04:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20900: ----------------------------------- Priority: Minor (was: Major) > why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20900 > URL: https://issues.jboss.org/browse/JBIDE-20900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > When publishing, we use this: > {code} > [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final > -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200" > -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true > -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip > -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources > -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack > {code} > But there's also this: > {code} > [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz > [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz > [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz > [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz (25 KB at 99.3 KB/sec) > [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes "" > [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code} > So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 06:55:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Fri, 2 Oct 2015 06:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20880) Visual Editor New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov closed JBIDE-20880. ------------------------------------------ Assignee: Konstantin Marmalyukov Resolution: Rejected > Visual Editor New and Noteworthy for 4.3.0.Final > ------------------------------------------------ > > Key: JBIDE-20880 > URL: https://issues.jboss.org/browse/JBIDE-20880 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Alexey Kazakov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22visual-page-editor-templates%22%2C%22visual-page-editor-core%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 06:55:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Fri, 2 Oct 2015 06:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20891) BrowserSim New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov closed JBIDE-20891. ------------------------------------------ Assignee: Konstantin Marmalyukov Resolution: Rejected > BrowserSim New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20891 > URL: https://issues.jboss.org/browse/JBIDE-20891 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Alexey Kazakov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22browsersim%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 07:20:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 2 Oct 2015 07:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20796) neon update sites gets added out of the blue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBIDE-20796: ---------------------------------------- Fix Version/s: 4.3.1.Final > neon update sites gets added out of the blue > -------------------------------------------- > > Key: JBIDE-20796 > URL: https://issues.jboss.org/browse/JBIDE-20796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.1.Final > > Attachments: update-sites.png, update.png > > > When I removed *all* updatesites and added just http://download.jboss.org/jbosstools/mars/development/updates/ (should have just mars cr1), install and then ran check for update my updatesites contained neon references. > See https://www.dropbox.com/s/xo040iyhiw9zhsw/Screenshot%202015-09-24%2009.41.01.png?dl=0 > I'm not sure if I even needed to do the check for updates, but those are the steps I did. > note: I install *everything* and uncheck the "check all updatesites" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 08:17:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 2 Oct 2015 08:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20889) javascript New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114538#comment-13114538 ] Ilya Buziuk commented on JBIDE-20889: ------------------------------------- Nothing new for javascript-bower, [~vrubezhny] ? > javascript New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20889 > URL: https://issues.jboss.org/browse/JBIDE-20889 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, javascript-bower > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22javascript-bower%22%2C%22javascript%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 08:39:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Fri, 2 Oct 2015 08:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-513) JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-513: --------------------------------------- Summary: JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie Key: JBTIS-513 URL: https://issues.jboss.org/browse/JBTIS-513 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution, drools/ jBPM Affects Versions: 8.0.4.CR1 Reporter: Andrej Podhradsky Priority: Blocker At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see the there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 08:40:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Fri, 2 Oct 2015 08:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-513) JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-513: ------------------------------------ Description: At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see that there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 (was: At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see the there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1) > JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie > ---------------------------------------------------------------- > > Key: JBTIS-513 > URL: https://issues.jboss.org/browse/JBTIS-513 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, drools/ jBPM > Affects Versions: 8.0.4.CR1 > Reporter: Andrej Podhradsky > Priority: Blocker > > At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see that there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 08:42:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 2 Oct 2015 08:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20842) Need to implement npm support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114547#comment-13114547 ] Ilya Buziuk commented on JBIDE-20842: ------------------------------------- After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * org.jboss.tools.jst.js.node (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * org.jsboss.tools.jst.js.bower (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) I think it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). It it sounds good I will create another issue for refactoring. > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 08:43:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 2 Oct 2015 08:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20842) Need to implement npm support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114547#comment-13114547 ] Ilya Buziuk edited comment on JBIDE-20842 at 10/2/15 8:42 AM: -------------------------------------------------------------- After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) I think it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). It it sounds good I will create another issue for refactoring. was (Author: ibuziuk): After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * org.jboss.tools.jst.js.node (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * org.jsboss.tools.jst.js.bower (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) I think it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). It it sounds good I will create another issue for refactoring. > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 08:53:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 2 Oct 2015 08:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114555#comment-13114555 ] Paul Leacu commented on JBTIS-504: ---------------------------------- Hey [~nickboldt] - It's time to enable the EA components. So clearly I'll re-enable them in the early access discovery plugin.xml. My question is what to do with the existing "not available" released-side discovery plugin.xml. See comment: https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110988 If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access. Or does "not available" only apply to the release discovery plugin - thus I would keep all of the "not available" connectors and simply change the descriptor text to something like "Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x" > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 08:57:00 2015 From: issues at jboss.org (Rastislav Wagner (JIRA)) Date: Fri, 2 Oct 2015 08:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114559#comment-13114559 ] Rastislav Wagner commented on JBDS-2948: ---------------------------------------- [~akazakov] Can we move this JIRA to target 9.x ? > Improve Performance of small and large projects > ----------------------------------------------- > > Key: JBDS-2948 > URL: https://issues.jboss.org/browse/JBDS-2948 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Rastislav Wagner > Labels: f2f2014 > Fix For: 9.0.0.GA > > > Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues. > Unfortunately perceived issues for the user feels just as slow as real issues. > Suggestion: > Look in jira for performance issues and add "performance" label to them > Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings > Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse. > Setup goals to reach for these performance measurements. > Don?t add new features that make performance worse. For example don?t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 09:14:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 2 Oct 2015 09:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114574#comment-13114574 ] Snjezana Peco commented on JBIDE-20844: --------------------------------------- The PR fixes the issue in the following way: - if the maven importer hasn't imported a project (the project doesn't contain pom.xml, for instance), check if the project contains the .project file and, if it does, import it as a simple Eclipse project - if the project hasn't been imported, the Project Ready wizard will write the following message: 'XXX' project hasn't been imported. Check if it is defined correctly. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 09:14:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 2 Oct 2015 09:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114574#comment-13114574 ] Snjezana Peco edited comment on JBIDE-20844 at 10/2/15 9:13 AM: ---------------------------------------------------------------- The PR fixes the issue in the following way: - if the maven importer hasn't imported a project (the project doesn't contain pom.xml, for instance), check if the project contains the .project file and, if it does, import it as a simple Eclipse project - if the project hasn't been imported yet, the Project Ready wizard will write the following message: 'XXX' project hasn't been imported. Check if it is defined correctly. was (Author: snjeza): The PR fixes the issue in the following way: - if the maven importer hasn't imported a project (the project doesn't contain pom.xml, for instance), check if the project contains the .project file and, if it does, import it as a simple Eclipse project - if the project hasn't been imported, the Project Ready wizard will write the following message: 'XXX' project hasn't been imported. Check if it is defined correctly. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 09:15:03 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 2 Oct 2015 09:15:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco reassigned JBIDE-20844: ------------------------------------- Assignee: Alexey Kazakov (was: Snjezana Peco) Could you, please, review the PR? > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Alexey Kazakov > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 09:23:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 2 Oct 2015 09:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-513) JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-513: -------------------------------- Assignee: Paul Leacu > JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie > ---------------------------------------------------------------- > > Key: JBTIS-513 > URL: https://issues.jboss.org/browse/JBTIS-513 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, drools/ jBPM > Affects Versions: 8.0.4.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see that there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:04:00 2015 From: issues at jboss.org (Lucia Jelinkova (JIRA)) Date: Fri, 2 Oct 2015 10:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucia Jelinkova closed JBDS-3285. --------------------------------- Verified with JBDS 9.0 CR1. The EI is able to import non Eclipse projects. > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Len DiMaggio > Labels: new_and_noteworthy, usability > Fix For: 9.0.0.Alpha2 > > Attachments: import-me.zip > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:12:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 10:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: Fred Bricon created JBIDE-20902: ----------------------------------- Summary: Application Wizard: required template parameters from previously selected templates are shown Key: JBIDE-20902 URL: https://issues.jboss.org/browse/JBIDE-20902 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Fred Bricon Priority: Blocker When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: - required param reported in error, but is not listed - decoration does not match error displayed - can't go to next page as validation is impossible to achieve The eap6-basic-template should work OOTB. When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:12:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 10:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20902: ----------------------------------- Assignee: Andre Dietisheim > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:13:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 10:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20902: -------------------------------- Description: When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: - required param reported in error, but is not listed - decoration does not match error displayed - can't go to next page as validation is impossible to achieve !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png! The eap6-basic-template should work OOTB. When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. The only workaround is to close the wizard and make sure you directly select the proper template on the first try. was: When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: - required param reported in error, but is not listed - decoration does not match error displayed - can't go to next page as validation is impossible to achieve The eap6-basic-template should work OOTB. When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. The only workaround is to close the wizard and make sure you directly select the proper template on the first try. > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:13:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 10:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20902: -------------------------------- Description: When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: - required param reported in error, but is not listed - decoration does not match error displayed - can't go to next page as validation is impossible to achieve !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! The eap6-basic-template should work OOTB. When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. The only workaround is to close the wizard and make sure you directly select the proper template on the first try. was: When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: - required param reported in error, but is not listed - decoration does not match error displayed - can't go to next page as validation is impossible to achieve !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png! The eap6-basic-template should work OOTB. When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. The only workaround is to close the wizard and make sure you directly select the proper template on the first try. > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:28:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 10:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114651#comment-13114651 ] Fred Bricon commented on JBIDE-20902: ------------------------------------- In order to test the new templates - setup vagrant: https://github.com/fabric8io/fabric8-installer/tree/master/vagrant/openshift - download the raw Vagrantfile from https://github.com/fbricon/jctoolbox/blob/patch-1/openshift/Vagrantfile - In the directory containing that Vagrantfile, execute `vagrant up` - connect to the OS3 instance using basic auth: admin/admin > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:39:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 10:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20902: ----------------------------------- Issue Type: Bug (was: Feature Request) > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 10:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20902: ----------------------------------- Fix Version/s: 4.3.0.Final > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 10:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20902: ----------------------------------- Labels: respin-b (was: ) > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:50:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Fri, 2 Oct 2015 10:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114663#comment-13114663 ] Koen Aers commented on JBIDE-20801: ----------------------------------- it is better to squash the two commits into one commit and open a new pull request > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:50:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 2 Oct 2015 10:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20884: ----------------------------------- Assignee: Fred Bricon > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22openshift%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 10:51:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Fri, 2 Oct 2015 10:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114663#comment-13114663 ] Koen Aers edited comment on JBIDE-20801 at 10/2/15 10:50 AM: ------------------------------------------------------------- It is better to squash the two commits into one commit and open a new pull request. And cancel the old pull request. was (Author: koen.aers): it is better to squash the two commits into one commit and open a new pull request > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:16:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 2 Oct 2015 11:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114685#comment-13114685 ] Nick Boldt commented on JBIDE-20902: ------------------------------------ When the fix for this is committed, please push the Build button here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/build?delay=0sec > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:22:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Fri, 2 Oct 2015 11:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20836) Xcodebuild is failing with cordova-ios >= 3.9.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Srna closed JBIDE-20836. ------------------------------ Verified in JBT 4.3.0.CR2a build. > Xcodebuild is failing with cordova-ios >= 3.9.0 > ----------------------------------------------- > > Key: JBIDE-20836 > URL: https://issues.jboss.org/browse/JBIDE-20836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-a > Fix For: 4.3.0.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478645 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:26:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Fri, 2 Oct 2015 11:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114696#comment-13114696 ] Pavol Srna commented on TOOLSDOC-683: ------------------------------------- I confirm the patch in https://issues.jboss.org/browse/JBIDE-20836 works. And the tooling now supports running cordova in version 3.9.0 and 3.9.1. [~mhusnain], I've looked on the draft, please add version 3.9.1 for iOS too. Thanks. > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 11:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20889) javascript New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20889: -------------------------------------- Assignee: Victor Rubezhny > javascript New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20889 > URL: https://issues.jboss.org/browse/JBIDE-20889 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, javascript-bower > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22javascript-bower%22%2C%22javascript%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:32:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 11:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20842) Need to implement npm support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114699#comment-13114699 ] Alexey Kazakov commented on JBIDE-20842: ---------------------------------------- Makes sense. > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:33:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 11:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-2948: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) > Improve Performance of small and large projects > ----------------------------------------------- > > Key: JBDS-2948 > URL: https://issues.jboss.org/browse/JBDS-2948 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Rastislav Wagner > Labels: f2f2014 > Fix For: 9.0.1.GA > > > Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues. > Unfortunately perceived issues for the user feels just as slow as real issues. > Suggestion: > Look in jira for performance issues and add "performance" label to them > Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings > Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse. > Setup goals to reach for these performance measurements. > Don?t add new features that make performance worse. For example don?t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:33:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 11:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-2948: --------------------------------- Target Release: 9.0.1.GA (was: 9.0.0.GA) > Improve Performance of small and large projects > ----------------------------------------------- > > Key: JBDS-2948 > URL: https://issues.jboss.org/browse/JBDS-2948 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Rastislav Wagner > Labels: f2f2014 > Fix For: 9.0.1.GA > > > Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues. > Unfortunately perceived issues for the user feels just as slow as real issues. > Suggestion: > Look in jira for performance issues and add "performance" label to them > Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings > Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse. > Setup goals to reach for these performance measurements. > Don?t add new features that make performance worse. For example don?t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:36:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 2 Oct 2015 11:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower In-Reply-To: References: Message-ID: Ilya Buziuk created JBIDE-20903: ----------------------------------- Summary: Need to split org.jboss.tools.jst.js to *.node and *.bower Key: JBIDE-20903 URL: https://issues.jboss.org/browse/JBIDE-20903 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: javascript, javascript-bower Affects Versions: 4.3.0.CR1 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:37:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 2 Oct 2015 11:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20903: -------------------------------- Description: After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). > Need to split org.jboss.tools.jst.js to *.node and *.bower > ---------------------------------------------------------- > > Key: JBIDE-20903 > URL: https://issues.jboss.org/browse/JBIDE-20903 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: > * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) > * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) > it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:38:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 2 Oct 2015 11:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20842) Need to implement npm support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114703#comment-13114703 ] Ilya Buziuk commented on JBIDE-20842: ------------------------------------- [~akazakov], great, have created a separate one for refactoring JBIDE-20903 > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:49:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 2 Oct 2015 11:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20796) neon update sites gets added out of the blue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114712#comment-13114712 ] Nick Boldt commented on JBIDE-20796: ------------------------------------ For the Eclipse install where you say this weird behaviour (if you still have that Eclipse install available), try this: 1. rm -fr ~/.eclipse/org.eclipse.oomph.* 2. restart that Eclipse install. I'm betting even if you *could* reproduce the problem before purging the oomph metadata, it'll be gone afterwards. > neon update sites gets added out of the blue > -------------------------------------------- > > Key: JBIDE-20796 > URL: https://issues.jboss.org/browse/JBIDE-20796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.1.Final > > Attachments: update-sites.png, update.png > > > When I removed *all* updatesites and added just http://download.jboss.org/jbosstools/mars/development/updates/ (should have just mars cr1), install and then ran check for update my updatesites contained neon references. > See https://www.dropbox.com/s/xo040iyhiw9zhsw/Screenshot%202015-09-24%2009.41.01.png?dl=0 > I'm not sure if I even needed to do the check for updates, but those are the steps I did. > note: I install *everything* and uncheck the "check all updatesites" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:56:00 2015 From: issues at jboss.org (Victor Rubezhny (JIRA)) Date: Fri, 2 Oct 2015 11:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20889) javascript New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114715#comment-13114715 ] Victor Rubezhny commented on JBIDE-20889: ----------------------------------------- [~ibuziuk], [~akazakov] I believe we have nothing new for 4.3.0.Final > javascript New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20889 > URL: https://issues.jboss.org/browse/JBIDE-20889 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, javascript-bower > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22javascript-bower%22%2C%22javascript%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 12:01:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 12:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20889) javascript New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20889. ---------------------------------- Resolution: Rejected > javascript New and Noteworthy for 4.3.0.Final > --------------------------------------------- > > Key: JBIDE-20889 > URL: https://issues.jboss.org/browse/JBIDE-20889 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, javascript-bower > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22javascript-bower%22%2C%22javascript%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 12:52:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 2 Oct 2015 12:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19729) Version Auditing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-19729: ------------------------------- Fix Version/s: 4.4.0.Final (was: 4.3.0.Final) > Version Auditing > ---------------- > > Key: JBIDE-19729 > URL: https://issues.jboss.org/browse/JBIDE-19729 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > Epic to track issues related to auditing and quality control. > This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 12:52:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 2 Oct 2015 12:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19730) Build Improvement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-19730: ------------------------------- Fix Version/s: 4.4.0.Final (was: 4.3.0.Final) > Build Improvement > ----------------- > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > Epic to track issues related to improving how we release software. > This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 13:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 2 Oct 2015 13:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20904: ---------------------------------- Summary: create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable Key: JBIDE-20904 URL: https://issues.jboss.org/browse/JBIDE-20904 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt Suggestion: rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/9.x Examples of using a series of commands in parallel w/ a wait at the end: http://stackoverflow.com/questions/19543139/bash-script-processing-commands-in-parallel {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# {code} More discussion: {quote} [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: * add && after the 1st rsync in each loop * add & after the last one * put a wait after the last loop * give the big piece of code to procede directly to bash {quote} After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 13:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 2 Oct 2015 13:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20904: ---------------------------------- Assignee: Nick Boldt > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/9.x > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-commands-in-parallel > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 13:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 2 Oct 2015 13:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20904: ------------------------------- Fix Version/s: 4.4.0.Alpha1 > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/9.x > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-commands-in-parallel > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 13:23:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Fri, 2 Oct 2015 13:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "page-include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon updated JBIDE-20851: ---------------------------------- Summary: Skip Final NN aggregation page if "page-include-previous: false" (was: Skip Final NN aggregation page if "include-previous: false") > Skip Final NN aggregation page if "page-include-previous: false" > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 13:23:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Fri, 2 Oct 2015 13:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20851) Skip Final NN aggregation page if "page-include-previous: false" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon updated JBIDE-20851: ---------------------------------- Description: Add an attribute check i.e. "page-include-previous: " If false then skip the final aggregation and use this only doc as a final N&N. If true (default value) then aggregate all N&N docs (including this one). was: Add an attribute check i.e. "include-previous: " If false then skip the final aggregation and use this only doc as a final N&N. If true (default value) then aggregate all N&N docs (including this one). > Skip Final NN aggregation page if "page-include-previous: false" > ---------------------------------------------------------------- > > Key: JBIDE-20851 > URL: https://issues.jboss.org/browse/JBIDE-20851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > Add an attribute check i.e. "page-include-previous: " > If false then skip the final aggregation and use this only doc as a final N&N. > If true (default value) then aggregate all N&N docs (including this one). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 15:26:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 15:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20893) Docker New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20893: -------------------------------------- Assignee: Xavier Coulon > Docker New and Noteworthy for 4.3.0.Final > ----------------------------------------- > > Key: JBIDE-20893 > URL: https://issues.jboss.org/browse/JBIDE-20893 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22docker%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 15:26:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 15:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20881) Aerogear New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20881: -------------------------------------- Assignee: Gorkem Ercan > Aerogear New and Noteworthy for 4.3.0.Final > ------------------------------------------- > > Key: JBIDE-20881 > URL: https://issues.jboss.org/browse/JBIDE-20881 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Alexey Kazakov > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22aerogear-hybrid%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 15:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 15:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20886) Live Reload New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20886: -------------------------------------- Assignee: Xavier Coulon > Live Reload New and Noteworthy for 4.3.0.Final > ---------------------------------------------- > > Key: JBIDE-20886 > URL: https://issues.jboss.org/browse/JBIDE-20886 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22livereload%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 15:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 15:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20887) hibernate New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20887: -------------------------------------- Assignee: Koen Aers > hibernate New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20887 > URL: https://issues.jboss.org/browse/JBIDE-20887 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Alexey Kazakov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22hibernate%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 15:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 15:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20896) Webservices and Rest New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20896: -------------------------------------- Assignee: Xavier Coulon > Webservices and Rest New and Noteworthy for 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-20896 > URL: https://issues.jboss.org/browse/JBIDE-20896 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22webservices%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 15:58:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 15:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20905) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-20905: ---------------------------------------- Summary: Application Wizard: required template parameters from previously selected templates are shown Key: JBIDE-20905 URL: https://issues.jboss.org/browse/JBIDE-20905 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Fred Bricon Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.3.0.Final When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: - required param reported in error, but is not listed - decoration does not match error displayed - can't go to next page as validation is impossible to achieve !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! The eap6-basic-template should work OOTB. When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 15:59:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 15:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20905) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20905: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.0.Final) > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20905 > URL: https://issues.jboss.org/browse/JBIDE-20905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 16:00:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 2 Oct 2015 16:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20906) [portlet] Update parent pom reference to latest TP based on Neon In-Reply-To: References: Message-ID: Denis Golovin created JBIDE-20906: ------------------------------------- Summary: [portlet] Update parent pom reference to latest TP based on Neon Key: JBIDE-20906 URL: https://issues.jboss.org/browse/JBIDE-20906 Project: Tools (JBoss Tools) Issue Type: Task Components: portal-gatein Affects Versions: 4.4.0.Alpha1 Reporter: Denis Golovin Fix For: 4.4.0.Alpha1 As Max pointed out, there are no changes in code base and in JBoss Tools p2 repository assembly we use latest released portlet version, but we should build it against latest Eclipse Neon in TP to catch at least compilation problems (if any) related to new Eclipse release stream. It is required, because portlet is available though JBoss Central in nightly builds from master and we have to be sure it is usable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 16:01:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 2 Oct 2015 16:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20906) [portlet] Update parent pom reference to latest TP based on Neon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin resolved JBIDE-20906. ----------------------------------- Resolution: Done Released to master branch https://github.com/jbosstools/jbosstools-portlet/commit/591451a8c48d544f00ffc2dc71218837a9117789 > [portlet] Update parent pom reference to latest TP based on Neon > ---------------------------------------------------------------- > > Key: JBIDE-20906 > URL: https://issues.jboss.org/browse/JBIDE-20906 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: portal-gatein > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > As Max pointed out, there are no changes in code base and in JBoss Tools p2 repository assembly we use latest released portlet version, but we should build it against latest Eclipse Neon in TP to catch at least compilation problems (if any) related to new Eclipse release stream. > It is required, because portlet is available though JBoss Central in nightly builds from master and we have to be sure it is usable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 16:20:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 16:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20905) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20905: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/787 (was: https://github.com/jbosstools/jbosstools-openshift/pull/786) > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20905 > URL: https://issues.jboss.org/browse/JBIDE-20905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 16:57:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 16:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114771#comment-13114771 ] Andre Dietisheim commented on JBIDE-20902: ------------------------------------------ merged and pushed to upstream/jbosstools-4.3.x and upstream/jbosstools-4.3.1.x > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 16:58:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 16:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20905) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114772#comment-13114772 ] Andre Dietisheim commented on JBIDE-20905: ------------------------------------------ merged and pushed to upstream/master > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20905 > URL: https://issues.jboss.org/browse/JBIDE-20905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 17:11:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 17:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114773#comment-13114773 ] Andre Dietisheim commented on JBIDE-20902: ------------------------------------------ I triggered jenkins which completed build #50 successfully: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/50/ !build-50-build.png! > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > Attachments: build-50-build.png > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 17:11:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 2 Oct 2015 17:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20902: ------------------------------------- Attachment: build-50-build.png > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > Attachments: build-50-build.png > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 18:12:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 2 Oct 2015 18:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114780#comment-13114780 ] Alexey Kazakov commented on JBIDE-20902: ---------------------------------------- Thank you guys! > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > Attachments: build-50-build.png > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 19:16:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 2 Oct 2015 19:16:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20689) Skip tests that cannot run on current platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin reassigned JBIDE-20689: ------------------------------------- Assignee: Denis Golovin (was: Konstantin Marmalyukov) > Skip tests that cannot run on current platform > ---------------------------------------------- > > Key: JBIDE-20689 > URL: https://issues.jboss.org/browse/JBIDE-20689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.4.x > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.x > > > VPE related run without errors only only on certain platforms. They should be skipped during tests execution and appear as skipped in report. As an example javaee tests now fail to pass under Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 20:47:00 2015 From: issues at jboss.org (Gorkem Ercan (JIRA)) Date: Fri, 2 Oct 2015 20:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20881) Aerogear New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gorkem Ercan closed JBIDE-20881. -------------------------------- Resolution: Done > Aerogear New and Noteworthy for 4.3.0.Final > ------------------------------------------- > > Key: JBIDE-20881 > URL: https://issues.jboss.org/browse/JBIDE-20881 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Alexey Kazakov > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22aerogear-hybrid%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 20:47:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Fri, 2 Oct 2015 20:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20907) Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ In-Reply-To: References: Message-ID: Len DiMaggio created JBIDE-20907: ------------------------------------ Summary: Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ Key: JBIDE-20907 URL: https://issues.jboss.org/browse/JBIDE-20907 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: qa Affects Versions: 4.3.0.CR2 Reporter: Len DiMaggio Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 20:47:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Fri, 2 Oct 2015 20:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20907) Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio reassigned JBIDE-20907: ------------------------------------ Assignee: Len DiMaggio > Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20907 > URL: https://issues.jboss.org/browse/JBIDE-20907 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 20:52:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Fri, 2 Oct 2015 20:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20907) Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114790#comment-13114790 ] Len DiMaggio commented on JBIDE-20907: -------------------------------------- https://github.com/jbosstools/jbosstools-integration-tests/pull/1170 > Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20907 > URL: https://issues.jboss.org/browse/JBIDE-20907 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 3 07:35:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Sat, 3 Oct 2015 07:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20904: ----------------------------------- Issue Type: Enhancement (was: Bug) > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/9.x > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-commands-in-parallel > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 3 08:01:03 2015 From: issues at jboss.org (Daniel Dekany (JIRA)) Date: Sat, 3 Oct 2015 08:01:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20385) Upgrade FreeMarker to 2.3.23 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114795#comment-13114795 ] Daniel Dekany commented on JBIDE-20385: --------------------------------------- Thank you for fixing this, but can't this be put into 4.3.0 somehow, so that people get this from Eclipse Marketplace earlier? I guess there's code freeze for new features at this point, but it's a low risk change. As the current FreeMarker maintainer, I'm always using the plugin with up-to-date (even nightly) FreeMarker, so it's tested that it doesn't break the plugin. BTW, JBIDE-20491 is another trivial change that would be good to shoe in. > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20385 > URL: https://issues.jboss.org/browse/JBIDE-20385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 3 09:10:00 2015 From: issues at jboss.org (Dmitry Bocharov (JIRA)) Date: Sat, 3 Oct 2015 09:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Bocharov updated JBIDE-20801: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-hibernate/pull/79 (was: https://github.com/jbosstools/jbosstools-hibernate/pull/78) > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 3 09:10:00 2015 From: issues at jboss.org (Dmitry Bocharov (JIRA)) Date: Sat, 3 Oct 2015 09:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114796#comment-13114796 ] Dmitry Bocharov commented on JBIDE-20801: ----------------------------------------- done > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 4 21:50:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Sun, 4 Oct 2015 21:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20908) Upgrade FreeMarker to 2.3.23 In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20908: -------------------------------------- Summary: Upgrade FreeMarker to 2.3.23 Key: JBIDE-20908 URL: https://issues.jboss.org/browse/JBIDE-20908 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: freemarker Reporter: Daniel Dekany Assignee: Denis Golovin Fix For: 4.4.0.Alpha1 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 4 21:50:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Sun, 4 Oct 2015 21:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20908) Upgrade FreeMarker to 2.3.23 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20908: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.4.0.Alpha1) > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20908 > URL: https://issues.jboss.org/browse/JBIDE-20908 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.1.Final > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 4 21:50:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Sun, 4 Oct 2015 21:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20908) Upgrade FreeMarker to 2.3.23 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20908: ----------------------------------- Release Notes Text: (was: Released to master.) > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20908 > URL: https://issues.jboss.org/browse/JBIDE-20908 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.1.Final > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 4 21:52:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Sun, 4 Oct 2015 21:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20385) Upgrade FreeMarker to 2.3.23 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114814#comment-13114814 ] Alexey Kazakov commented on JBIDE-20385: ---------------------------------------- It's too late to fix it in JBoss Tools 4.3.0 but I think we can update it in the next maintenance release 4.3.1. I created a new issue for that - JBIDE-20908 > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20385 > URL: https://issues.jboss.org/browse/JBIDE-20385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 03:34:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Mon, 5 Oct 2015 03:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20886) Live Reload New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon closed JBIDE-20886. --------------------------------- Release Notes Text: no specific N&N for 4.3.0.Final Resolution: Rejected > Live Reload New and Noteworthy for 4.3.0.Final > ---------------------------------------------- > > Key: JBIDE-20886 > URL: https://issues.jboss.org/browse/JBIDE-20886 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22livereload%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 03:38:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Mon, 5 Oct 2015 03:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20896) Webservices and Rest New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114843#comment-13114843 ] Xavier Coulon commented on JBIDE-20896: --------------------------------------- [~bfitzpat], [~scabanovich], do you have any specific N&N for 4.3.0.Final ? > Webservices and Rest New and Noteworthy for 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-20896 > URL: https://issues.jboss.org/browse/JBIDE-20896 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22webservices%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 03:52:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Mon, 5 Oct 2015 03:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter closed JBDS-3532. ----------------------------- Verified for 9.0.0.CR2a, closing. > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/ > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 04:27:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Mon, 5 Oct 2015 04:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20895) Core/General New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlado Pakan closed JBIDE-20895. ------------------------------- Verified > Core/General New and Noteworthy for 4.3.0.Final > ----------------------------------------------- > > Key: JBIDE-20895 > URL: https://issues.jboss.org/browse/JBIDE-20895 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22common%2Fjst%2Fcore%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 04:31:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 5 Oct 2015 04:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114855#comment-13114855 ] Supriya Bharadwaj commented on TOOLSDOC-610: -------------------------------------------- > Made few changes in the md file and saved as DRAFT on Portal (https://access.redhat.com/node/1518153/draft) > Made changes in the adoc file to: >> Rectify numbering >> Renamed file as per community version >> Tallied file with the checklist >> File and images sent to Misha > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 04:32:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Mon, 5 Oct 2015 04:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20877) jst/jsf New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlado Pakan closed JBIDE-20877. ------------------------------- Verified > jst/jsf New and Noteworthy for 4.3.0.Final > ------------------------------------------ > > Key: JBIDE-20877 > URL: https://issues.jboss.org/browse/JBIDE-20877 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22jsf%22%2C%22jsp%2Fjsf%2Fxml%2Fhtml-source-editing%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 04:34:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 5 Oct 2015 04:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj updated TOOLSDOC-610: --------------------------------------- Attachment: hmt_icon_modified.png hmt_config_file_icon_modified.png hmt_firstapp.adoc Hi [~mhusnain], can you please post these upstream? Thanks - Supriya > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > Attachments: hmt_config_file_icon_modified.png, hmt_firstapp.adoc, hmt_icon_modified.png > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 04:38:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Mon, 5 Oct 2015 04:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20909) Mistype errors in General What's New in 4.3.0.Final In-Reply-To: References: Message-ID: Vlado Pakan created JBIDE-20909: ----------------------------------- Summary: Mistype errors in General What's New in 4.3.0.Final Key: JBIDE-20909 URL: https://issues.jboss.org/browse/JBIDE-20909 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.Final Environment: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html#general Reporter: Vlado Pakan * 'JBoss Tools new integrate new' -> 'JBoss Tools now integrate new' * 'best inside ythe IDE' -> 'best inside the IDE' * 'user isn?t required how to import' -> 'user isn?t required to know how to import' -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 04:53:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Mon, 5 Oct 2015 04:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114865#comment-13114865 ] Mari?n Labuda commented on JBIDE-20902: --------------------------------------- [~fbricon] in step 3 to set up an OpenShift instance I had to use parameter "--provider=virtualbox", otherwise it used libvirt by default. So to pass step 3 it's, in some cases, required to use "vagrant up --provider=virtualbox" > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > Attachments: build-50-build.png > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:02:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 5 Oct 2015 05:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: Martin Malina created JBDS-3535: ----------------------------------- Summary: Installer progress looks bad with OS X El Capitan Key: JBDS-3535 URL: https://issues.jboss.org/browse/JBDS-3535 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 9.0.0.CR2 Reporter: Martin Malina It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). It is now a narrow stripe and the text that we display over it does not look nice. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:03:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 5 Oct 2015 05:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina updated JBDS-3535: -------------------------------- Attachment: install-progress.png > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:03:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 5 Oct 2015 05:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina updated JBDS-3535: -------------------------------- Description: It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). It is now a narrow stripe and the text that we display over it does not look nice. !install-progress.png! was: It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). It is now a narrow stripe and the text that we display over it does not look nice. > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:07:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Mon, 5 Oct 2015 05:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20879) Forge New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Srna closed JBIDE-20879. ------------------------------ Verified. > Forge New and Noteworthy for 4.3.0.Final > ---------------------------------------- > > Key: JBIDE-20879 > URL: https://issues.jboss.org/browse/JBIDE-20879 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22forge%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:17:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 5 Oct 2015 05:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114873#comment-13114873 ] Mickael Istria commented on JBIDE-20904: ---------------------------------------- I made a short test to verify that bash variable substitution happens early enough (to make sure that we can use the same "ID" variables in iteration with some good isolation: {code} mistria at mistria-laptop:~$ ID=1; sleep 2 && echo 1st=$ID & sleep 1 && ID=2 && echo 2nd=$ID; wait 2nd=2 1st=1 {code} Here we can see that what matters is the value at the variable while passing the instruction to bash, not when actually starting the instruction. > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/9.x > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-commands-in-parallel > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:18:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 5 Oct 2015 05:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114874#comment-13114874 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- Confirmed with Jan about this release being GA and not CR2 (cr2 build is being used internally) Added the CR1 ss in the Install JBDS BYOE when Online chapter (we can have an SS with GA only after it is released tomorrow and is available to be installed through the Eclipse Marketplace) Added an entry in the Rev History chapter Had Jan have a look at the install guide for his approval; he has given a go-ahead > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:20:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 5 Oct 2015 05:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114876#comment-13114876 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- Hi [~mhusnain], I have completed my work on the Install Guide. Details of doc: Content Spec ID: 23020 DocBuilder Link: http://docbuilder.usersys.redhat.com/23020/ Thanks - supriya > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:24:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Mon, 5 Oct 2015 05:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20695) tools.jboss.org/features: Add Bower In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Srna closed JBIDE-20695. ------------------------------ Verified. > tools.jboss.org/features: Add Bower > ----------------------------------- > > Key: JBIDE-20695 > URL: https://issues.jboss.org/browse/JBIDE-20695 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript-bower > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.3.0.Final > > > We should add our new Bower feature to tools.jboss.org/features. > Not sure if it should go to the existing HTML5/JS/CSS or we need a new JavaScript page? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:42:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 5 Oct 2015 05:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed JBIDE-20833. --------------------------------- I can confirm that JBDS 9.0.0.CR2 respin-b B124 includes build 24 of playground plugins: {code} org.jboss.tools.playground.easymport.jee_1.0.0.Final-v20150925-1225-B24.jar org.jboss.tools.playground.easymport.maven_1.0.0.Final-v20150925-1225-B24.jar {code} Closing. > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:46:01 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 5 Oct 2015 05:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20904: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build-ci/pull/137, https://github.com/jbdevstudio/jbdevstudio-devdoc/pull/131 (was: https://github.com/jbosstools/jbosstools-build-ci/pull/137) > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/9.x > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-commands-in-parallel > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 05:47:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 5 Oct 2015 05:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20904) create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114894#comment-13114894 ] Mickael Istria commented on JBIDE-20904: ---------------------------------------- I also have a proposal on the devdoc, to make it support parallel steps and be more looking like a script or a job config (ie refactoring what are the actual input value vs the "transient" ones) > create single bash script (and Jenkins job wrapper) to perform the first 10 steps of CI -> stage or stage -> development/stable > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/9.x > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-commands-in-parallel > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 06:14:01 2015 From: issues at jboss.org (Rastislav Wagner (JIRA)) Date: Mon, 5 Oct 2015 06:14:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20910) XLabelProvider$RootWrapper memory leak In-Reply-To: References: Message-ID: Rastislav Wagner created JBIDE-20910: ---------------------------------------- Summary: XLabelProvider$RootWrapper memory leak Key: JBIDE-20910 URL: https://issues.jboss.org/browse/JBIDE-20910 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.CR1 Reporter: Rastislav Wagner I see amount of XLabelProvider$RootWrapper instances just raising in numbers when importing/deleting projects -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 06:59:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 5 Oct 2015 06:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-20911: ------------------------------------------- Summary: open local terminal with oc already logged in Key: JBIDE-20911 URL: https://issues.jboss.org/browse/JBIDE-20911 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Max Rydahl Andersen it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. * This assumes users have oc in their path * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 07:01:02 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 5 Oct 2015 07:01:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114922#comment-13114922 ] Max Rydahl Andersen commented on JBIDE-20911: --------------------------------------------- testing bee. ``` system.out.println("maf"); ``` > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 07:01:02 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 5 Oct 2015 07:01:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBIDE-20911: ---------------------------------------- Comment: was deleted (was: testing bee. ``` system.out.println("maf"); ``` ) > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 07:28:00 2015 From: issues at jboss.org (Hardy Ferentschik (JIRA)) Date: Mon, 5 Oct 2015 07:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114933#comment-13114933 ] Hardy Ferentschik commented on JBIDE-20911: ------------------------------------------- {quote} This assumes users have oc in their path {quote} Would it not be somehow possible to use the _oc_ version provided by the virtual environment. This would mean one less thing to install. > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 07:31:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 5 Oct 2015 07:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114936#comment-13114936 ] Max Rydahl Andersen commented on JBIDE-20911: --------------------------------------------- not sure what you mean by virtual environment here ? the oc is supposed to be install on users local host. we could probably point to the oc binary users will eventually have to configure to do tail logs etc. > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 07:52:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Mon, 5 Oct 2015 07:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20902) Application Wizard: required template parameters from previously selected templates are shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda closed JBIDE-20902. --------------------------------- Verified in JBDS 9.0.0.CR2 respin b. Build ID B124. > Application Wizard: required template parameters from previously selected templates are shown > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20902 > URL: https://issues.jboss.org/browse/JBIDE-20902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Final > > Attachments: build-50-build.png > > > When connected to an openshift 3 instance having the latest middleware templates, that use required parameters, create a new Application. If you click on one template, like amq6-persistent-ssl, then select (dbl-click) the eap6-basic-s2i one, you'll see: > - required param reported in error, but is not listed > - decoration does not match error displayed > - can't go to next page as validation is impossible to achieve > !http://content.screencast.com/users/fbricon/folders/Jing/media/00a9d65b-c3a2-4651-89d8-9521ae8a7728/00000206.png|width=600! > The eap6-basic-template should work OOTB. > When selecting a template in the treeview, databinding populates validation requirements in the model, but these requirements are not reset when selecting another template. > The only workaround is to close the wizard and make sure you directly select the proper template on the first try. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 08:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20896) Webservices and Rest New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20896. ---------------------------------- Resolution: Rejected Nothing from Websockets. Closing this issue. [~bfitzpat] please reopen if you have anything new for JBT 4.3.0.Final. I don't see any changes in github though. > Webservices and Rest New and Noteworthy for 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-20896 > URL: https://issues.jboss.org/browse/JBIDE-20896 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22webservices%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:41:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 5 Oct 2015 08:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114971#comment-13114971 ] Martin Malina commented on TOOLSDOC-687: ---------------------------------------- Hi [~mhusnain], I started looking at the release notes and I have one question. Where are the RNs from 9.0.0.CR1? Looking at https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/ the CR1 version is there, but no docs. Shouldn't it be there? (For the record, I find it easier to have a previous version of RNs open when reviewing a new version, so that I can easily see what is actually changed and what is just carried over from the past.) > Review JBDS 9 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-687 > URL: https://issues.jboss.org/browse/TOOLSDOC-687 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Reporter: Misha Ali > Assignee: Martin Malina > > Please review here: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:42:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Mon, 5 Oct 2015 08:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: Vlado Pakan created JBIDE-20912: ----------------------------------- Summary: LiveReload is not disabled Key: JBIDE-20912 URL: https://issues.jboss.org/browse/JBIDE-20912 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim, cordovasim Affects Versions: 4.3.0.CR2 Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 Reporter: Vlado Pakan 1. Import HTML 5 project from JBoss Central 2. Run it on server 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' ASSERT: index.html page is opened in system web browser 4. Copy link with index.html from system web broweer to Browsersim ASSERT: LiveReload is enabled in BrowserSim context menu 5. Open index.html page in VPE, change content and save it ASSERT: Changes are rendered in BrowserSim and system web browser 6. Disable LiveReload in BrowserSim context menu 7. change content of index.html and save it ASSERT: Changes are rendered in system web browser ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:44:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 5 Oct 2015 08:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk reassigned JBIDE-20912: ----------------------------------- Assignee: Ilya Buziuk > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:49:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 5 Oct 2015 08:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20912: -------------------------------- Fix Version/s: 4.3.1.Final > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:52:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 08:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20909) Mistype errors in General What's New in 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20909. ------------------------------------ Fix Version/s: 4.3.0.Final Assignee: Alexey Kazakov Resolution: Done Fixed. Thanks! > Mistype errors in General What's New in 4.3.0.Final > --------------------------------------------------- > > Key: JBIDE-20909 > URL: https://issues.jboss.org/browse/JBIDE-20909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Final > Environment: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html#general > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.3.0.Final > > > * 'JBoss Tools new integrate new' -> 'JBoss Tools now integrate new' > * 'best inside ythe IDE' -> 'best inside the IDE' > * 'user isn?t required how to import' -> 'user isn?t required to know how to import' -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:53:00 2015 From: issues at jboss.org (Hardy Ferentschik (JIRA)) Date: Mon, 5 Oct 2015 08:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114978#comment-13114978 ] Hardy Ferentschik commented on JBIDE-20911: ------------------------------------------- {quote} not sure what you mean by virtual environment here ? the oc is supposed to be install on users local host. {quote} I thought about the virtualized environment as provided by the Developer Platform. I guess right now you indeed need the oc binary locally, because you cannot afaiu drive the communication with the Openshift 3 instance purely via its REST API (due to the problems with finding/implementing a Java client providing the required capabilities). If this problem could be solved, it should be possible to do all "local" communication via REST avoiding the need for the _oc_ cli altogether. If the user in such a case still wants to use the _oc_ command line and has the virtualized environment of the Developer Platform available, it should be possible to eg ssh to a virtual machine in this environment which provides the _oc_ cli. Anyways, just a thought. I hope it is clearer now what I meant. > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:56:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 08:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3535: ------------------------------------ Assignee: Denis Golovin > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Denis Golovin > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:57:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 5 Oct 2015 08:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114979#comment-13114979 ] Max Rydahl Andersen commented on JBIDE-20911: --------------------------------------------- well, we already run oc on the local host for the cases where you do not have a virtualbox running. if you want this terminal to be ssh'ing into vagrant then that is a different flavor of this feature. Could be done too - was thought kinda hoping the openshift tools would not need to know whether running in a vagrant box or remote.. > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:02:00 2015 From: issues at jboss.org (Hardy Ferentschik (JIRA)) Date: Mon, 5 Oct 2015 09:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114980#comment-13114980 ] Hardy Ferentschik commented on JBIDE-20911: ------------------------------------------- {quote} well, we already run oc on the local host for the cases where you do not have a virtualbox running. {quote} fair enough > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:06:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 5 Oct 2015 09:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114987#comment-13114987 ] Ilya Buziuk commented on JBIDE-20912: ------------------------------------- [~vpakan], this happens cause LiveReload was originally enabled and processed not on BrowserSim but on LiveReload side: Show In' > 'Web Browser via LiveReolad Server' runs server with LiveReload enabled and BrowserSim's LiveReload settings have no value as long as all requests are processed on LiveReload Server i.e for the url which is generated after 'Web Browser via LiveReolad Server' selection, LiveReload will be enabled for any browser. Need to think how can we reflect it in BrowserSim preferences > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:29:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 5 Oct 2015 09:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20911: ------------------------------------- Fix Version/s: 4.4.x > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.4.0.Alpha1 > > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:29:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 5 Oct 2015 09:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20911: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.4.0.Alpha1 > > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token= --server=` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:42:00 2015 From: issues at jboss.org (Brian Fitzpatrick (JIRA)) Date: Mon, 5 Oct 2015 09:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20896) Webservices and Rest New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115022#comment-13115022 ] Brian Fitzpatrick commented on JBIDE-20896: ------------------------------------------- Nothing here. > Webservices and Rest New and Noteworthy for 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-20896 > URL: https://issues.jboss.org/browse/JBIDE-20896 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22webservices%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:46:01 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Mon, 5 Oct 2015 09:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20887) hibernate New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers closed JBIDE-20887. ----------------------------- Resolution: Rejected > hibernate New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20887 > URL: https://issues.jboss.org/browse/JBIDE-20887 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Alexey Kazakov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22hibernate%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:47:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 09:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20910) XLabelProvider$RootWrapper memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20910: -------------------------------------- Assignee: Viacheslav Kabanovich > XLabelProvider$RootWrapper memory leak > -------------------------------------- > > Key: JBIDE-20910 > URL: https://issues.jboss.org/browse/JBIDE-20910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > I see amount of XLabelProvider$RootWrapper instances just raising in numbers when importing/deleting projects -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:47:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 09:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20910) XLabelProvider$RootWrapper memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20910: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 > XLabelProvider$RootWrapper memory leak > -------------------------------------- > > Key: JBIDE-20910 > URL: https://issues.jboss.org/browse/JBIDE-20910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > I see amount of XLabelProvider$RootWrapper instances just raising in numbers when importing/deleting projects -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 09:57:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 09:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20708) tools.jboss.org/features: Add Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115031#comment-13115031 ] Alexey Kazakov commented on JBIDE-20708: ---------------------------------------- [~mhusnain] could you please take a look at Xavier's PR? Thanks! > tools.jboss.org/features: Add Docker > ------------------------------------ > > Key: JBIDE-20708 > URL: https://issues.jboss.org/browse/JBIDE-20708 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > We should add Docker to tools.jboss.org/features -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:15:01 2015 From: issues at jboss.org (Martijn Dashorst (JIRA)) Date: Mon, 5 Oct 2015 10:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115050#comment-13115050 ] Martijn Dashorst commented on JBIDE-12365: ------------------------------------------ My workspace is now flooded with warnings: "JBoss Tools Knowledge Base problem: Nature is not installed on required Java project ?project?" As we strive for a zero-warning policy at our company, and this warning is the top in the warning view, how can I disable this check? And I don't have any plugin resembling the "JBoss Tools Knowledge Base" installed. > Enable JBoss Tools Knowledge Base support for dependencies > ---------------------------------------------------------- > > Key: JBIDE-12365 > URL: https://issues.jboss.org/browse/JBIDE-12365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: LATER > > > Suppose we have two maven projects. > One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). > The other is a plain java project. > The first one includes the second one as a dependency. > When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). > You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) > So CDI/Seam/JSF (KB included) should be enabled for the first project. > And KB should be enabled for the second one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 11:36:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 11:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115098#comment-13115098 ] Alexey Kazakov commented on JBIDE-12365: ---------------------------------------- org.jboss.tools.jst.web.kb is the JBoss Tools Knowledge Base plugin You can disable this validation in Project properties -> JBoss Tools Knowledge Base -> Validator for you project(s) or you can disable it for the whole workspace in Window -> Preferences -> JBoss Tools -> Web -> Knowledge Base -> Validator Or you can access these preferences using a quick fix for the validation problem. > Enable JBoss Tools Knowledge Base support for dependencies > ---------------------------------------------------------- > > Key: JBIDE-12365 > URL: https://issues.jboss.org/browse/JBIDE-12365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: LATER > > > Suppose we have two maven projects. > One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). > The other is a plain java project. > The first one includes the second one as a dependency. > When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). > You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) > So CDI/Seam/JSF (KB included) should be enabled for the first project. > And KB should be enabled for the second one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 11:57:00 2015 From: issues at jboss.org (Martijn Dashorst (JIRA)) Date: Mon, 5 Oct 2015 11:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115103#comment-13115103 ] Martijn Dashorst commented on JBIDE-12365: ------------------------------------------ These are disabled already, yet the warnings are still generated in my workspace. Removing the warnings from the problems view, and rebuilding my workspace resurfaces the warnings. There is no way to remove them and keep these warnings away. > Enable JBoss Tools Knowledge Base support for dependencies > ---------------------------------------------------------- > > Key: JBIDE-12365 > URL: https://issues.jboss.org/browse/JBIDE-12365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: LATER > > > Suppose we have two maven projects. > One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). > The other is a plain java project. > The first one includes the second one as a dependency. > When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). > You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) > So CDI/Seam/JSF (KB included) should be enabled for the first project. > And KB should be enabled for the second one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:00:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 5 Oct 2015 12:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115105#comment-13115105 ] Nick Boldt commented on JBTIS-504: ---------------------------------- {quote} If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access.{quote} Correct. No notavailable connector == no adver'teasing. You can certainly say {quote}"Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x"{quote} But a less verbose way might be: "Enable Early Access to install this. Also available in Red Hat JBoss Developer Studio 8." > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:00:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 5 Oct 2015 12:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115105#comment-13115105 ] Nick Boldt edited comment on JBTIS-504 at 10/5/15 11:59 AM: ------------------------------------------------------------ {quote}If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access.{quote} Correct. No notavailable connector == no adver'teasing. You can certainly say {quote}"Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x"{quote} But a less verbose way might be: "Enable Early Access to install this. Also available in Red Hat JBoss Developer Studio 8." was (Author: nickboldt): {quote} If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access.{quote} Correct. No notavailable connector == no adver'teasing. You can certainly say {quote}"Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x"{quote} But a less verbose way might be: "Enable Early Access to install this. Also available in Red Hat JBoss Developer Studio 8." > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:02:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 5 Oct 2015 12:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115106#comment-13115106 ] Martin Malina commented on TOOLSDOC-687: ---------------------------------------- ?2. About this Release It includes Eclipse Mars. - should say: Eclipse Mars.1 - FYI, Mars.1 is what would previously be called SR1 3. New Features This release of JBoss Developer Studio includes new features to enhance and extend its functionality as detailed here: (TBD) - remove the string "(TBD)" 4.1. Resolved Issues The query seems wrong. If you look at 8.1 release notes: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio/8.1/html-single/8.1.0_Release_Notes/index.html The idea is to show bugs that were logged against something older than any of the 9.0 milestones. Also, there is no 9.0.0.Final or 4.3.0.GA. So should be like this: {code} (project in (JBDS) AND affectedVersion < 9.0.0.Alpha1 AND fixVersion in (9.0.0.Alpha1, 9.0.0.Alpha2, 9.0.0.Beta1, 9.0.0.Beta2, 9.0.0.CR1, 9.0.0.CR2, 9.0.0.GA) OR project in (JBIDE) AND affectedVersion < 4.3.0.Alpha1 AND fixVersion in (4.3.0.Alpha1, 4.3.0.Alpha2, 4.3.0.Beta1, 4.3.0.Beta2, 4.3.0.Final)) AND type in (Bug) AND resolution in (Done) {code} Otherwise it looks ok. > Review JBDS 9 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-687 > URL: https://issues.jboss.org/browse/TOOLSDOC-687 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Reporter: Misha Ali > Assignee: Martin Malina > > Please review here: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:03:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 5 Oct 2015 12:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina reassigned TOOLSDOC-687: -------------------------------------- Assignee: Misha Ali (was: Martin Malina) Assigning back to Misha. > Review JBDS 9 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-687 > URL: https://issues.jboss.org/browse/TOOLSDOC-687 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Reporter: Misha Ali > Assignee: Misha Ali > > Please review here: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:06:00 2015 From: issues at jboss.org (Martijn Dashorst (JIRA)) Date: Mon, 5 Oct 2015 12:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115103#comment-13115103 ] Martijn Dashorst edited comment on JBIDE-12365 at 10/5/15 12:05 PM: -------------------------------------------------------------------- These are disabled already, yet the warnings are still generated in my workspace. Removing the warnings from the problems view, and rebuilding my workspace resurfaces the warnings. There is no way to remove them and keep these warnings away. If you want the exact setup, you can use a clean 4.5.1 mars "Java developers" (not Java EE) download, and import these plugins and features: https://github.com/topicusonderwijs/topicusonderwijs/blob/master/eclipse-mars.p2f We want to have a minimal setup so we try to install the bare minimum of plugins. Therefore we remove all handy tool integrations such as CDI and JPA validators. As we also don't use JSF, we really don't have a use case for JSF tools. etc. As far as I know, I can't remove the JBoss Standard Tools (which generates these warnings) from the setup because the other tools depend on it. was (Author: dashorst): These are disabled already, yet the warnings are still generated in my workspace. Removing the warnings from the problems view, and rebuilding my workspace resurfaces the warnings. There is no way to remove them and keep these warnings away. > Enable JBoss Tools Knowledge Base support for dependencies > ---------------------------------------------------------- > > Key: JBIDE-12365 > URL: https://issues.jboss.org/browse/JBIDE-12365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: LATER > > > Suppose we have two maven projects. > One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). > The other is a plain java project. > The first one includes the second one as a dependency. > When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). > You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) > So CDI/Seam/JSF (KB included) should be enabled for the first project. > And KB should be enabled for the second one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:14:00 2015 From: issues at jboss.org (Martijn Dashorst (JIRA)) Date: Mon, 5 Oct 2015 12:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115103#comment-13115103 ] Martijn Dashorst edited comment on JBIDE-12365 at 10/5/15 12:13 PM: -------------------------------------------------------------------- Somehow JBoss Tools instructed itself to enable the KB settings for some projects, causing the warning to appear that those projects depend on other projects without KB. How can I disable the KB setting for any project that I import? I hate for all developers in my company to have to go through this ordeal and have to uncheck 80 boxes individually. -deleted text-These are disabled already-deleted text-, yet the warnings are still generated in my workspace. Removing the warnings from the problems view, and rebuilding my workspace resurfaces the warnings. There is no way to remove them and keep these warnings away. If you want the exact setup, you can use a clean 4.5.1 mars "Java developers" (not Java EE) download, and import these plugins and features: https://github.com/topicusonderwijs/topicusonderwijs/blob/master/eclipse-mars.p2f We want to have a minimal setup so we try to install the bare minimum of plugins. Therefore we remove all handy tool integrations such as CDI and JPA validators. As we also don't use JSF, we really don't have a use case for JSF tools. etc. As far as I know, I can't remove the JBoss Standard Tools (which generates these warnings) from the setup because the other tools depend on it. was (Author: dashorst): These are disabled already, yet the warnings are still generated in my workspace. Removing the warnings from the problems view, and rebuilding my workspace resurfaces the warnings. There is no way to remove them and keep these warnings away. If you want the exact setup, you can use a clean 4.5.1 mars "Java developers" (not Java EE) download, and import these plugins and features: https://github.com/topicusonderwijs/topicusonderwijs/blob/master/eclipse-mars.p2f We want to have a minimal setup so we try to install the bare minimum of plugins. Therefore we remove all handy tool integrations such as CDI and JPA validators. As we also don't use JSF, we really don't have a use case for JSF tools. etc. As far as I know, I can't remove the JBoss Standard Tools (which generates these warnings) from the setup because the other tools depend on it. > Enable JBoss Tools Knowledge Base support for dependencies > ---------------------------------------------------------- > > Key: JBIDE-12365 > URL: https://issues.jboss.org/browse/JBIDE-12365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: LATER > > > Suppose we have two maven projects. > One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). > The other is a plain java project. > The first one includes the second one as a dependency. > When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). > You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) > So CDI/Seam/JSF (KB included) should be enabled for the first project. > And KB should be enabled for the second one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:17:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 5 Oct 2015 12:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115114#comment-13115114 ] Max Rydahl Andersen commented on JBIDE-20912: --------------------------------------------- im not following what is the error is here ? sounds like it works as expected ? (that when you load a page with livereload.js injected then livereload is enabled) > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:20:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Mon, 5 Oct 2015 12:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115115#comment-13115115 ] Vlado Pakan commented on JBIDE-20912: ------------------------------------- When LiveReload is disabled within BrowserSim (via BrowserSim context menu) web page displayed in BrowserSim is still redislpayed after web page is updated on file system. > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:21:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Mon, 5 Oct 2015 12:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115115#comment-13115115 ] Vlado Pakan edited comment on JBIDE-20912 at 10/5/15 12:20 PM: --------------------------------------------------------------- When LiveReload is disabled within BrowserSim (via BrowserSim context menu) web page displayed in BrowserSim is still redisplayed after web page is updated on file system. was (Author: vpakan): When LiveReload is disabled within BrowserSim (via BrowserSim context menu) web page displayed in BrowserSim is still redislpayed after web page is updated on file system. > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 12:22:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 5 Oct 2015 12:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115117#comment-13115117 ] Ilya Buziuk commented on JBIDE-20912: ------------------------------------- [~maxandersen], yeah what Vlado means is that BrowserSim settings (enable / disable LiveReload) not working in this case. LiveReload will be enabled anyways > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 13:14:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 13:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20913) Knowledge Base validation preference is ingnored In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20913: -------------------------------------- Summary: Knowledge Base validation preference is ingnored Key: JBIDE-20913 URL: https://issues.jboss.org/browse/JBIDE-20913 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.1.Final, 4.4.0.Alpha1 1. Create two java project, Project1 and Project2 2. Project1 depends on Project2 3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base) 4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2. 5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator 6. Uncheck Enable Validation 7. Clean/rebuild Project1 8. FAILURE: The warning is still there If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears. It looks like when we disable the KB validator at all then the old warning is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 13:18:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 13:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115143#comment-13115143 ] Alexey Kazakov commented on JBIDE-12365: ---------------------------------------- As I said you don't need to disable KB validation for every project in your worspace. Just disable it Preferences -> JBoss Tools -> Web -> Knowledge Base -> Validator and clean/rebuild your workspace. If you already have some warnings then this won't help (when you disable validation, the old warning are not removed). I have created a new issue for that bug - JBIDE-20913 As workaround you can set "Capabilities are not enabled in Java uitl module" to "Ignore" in Preferences -> JBoss Tools -> Web -> Knowledge Base -> Validator. Then clean/rebuild the workspace. It will remove the validtion warnings. KB is not for JSF2 only. It's more general and used by JSF, Batch and some other tooling too. JBoss Tools maven integration enables KB for Java EE maven projects automatically. You can disable this integration in Preferences -> JBoss Tools -> Maven integration. Seam, CDI, JSF integration it's what you need to disable if you don't want JBoss Tools automatically configure the corresponding maven projects. > Enable JBoss Tools Knowledge Base support for dependencies > ---------------------------------------------------------- > > Key: JBIDE-12365 > URL: https://issues.jboss.org/browse/JBIDE-12365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: LATER > > > Suppose we have two maven projects. > One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). > The other is a plain java project. > The first one includes the second one as a dependency. > When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). > You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) > So CDI/Seam/JSF (KB included) should be enabled for the first project. > And KB should be enabled for the second one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 13:49:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Mon, 5 Oct 2015 13:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20677) Cannot finish Install dialog called from central in some scenarios In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115155#comment-13115155 ] Snjezana Peco commented on JBIDE-20677: --------------------------------------- This is an upstream issue. I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=479063. > Cannot finish Install dialog called from central in some scenarios > ------------------------------------------------------------------ > > Key: JBIDE-20677 > URL: https://issues.jboss.org/browse/JBIDE-20677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR1 > Environment: Linux x86_64 gtk3 > Reporter: Denis Golovin > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: recording.mp4 > > > After pressing "Deselect All" and "Select All" buttons in Install dialog finish button is not available. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 13:50:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Mon, 5 Oct 2015 13:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20677) Cannot finish Install dialog called from central in some scenarios In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20677: ---------------------------------- Component/s: upstream > Cannot finish Install dialog called from central in some scenarios > ------------------------------------------------------------------ > > Key: JBIDE-20677 > URL: https://issues.jboss.org/browse/JBIDE-20677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Affects Versions: 4.3.0.CR1 > Environment: Linux x86_64 gtk3 > Reporter: Denis Golovin > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: recording.mp4 > > > After pressing "Deselect All" and "Select All" buttons in Install dialog finish button is not available. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 14:00:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 5 Oct 2015 14:00:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20914) make jbds-dist-diff more user-friendly and scriptable In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20914: ---------------------------------- Summary: make jbds-dist-diff more user-friendly and scriptable Key: JBIDE-20914 URL: https://issues.jboss.org/browse/JBIDE-20914 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.CR2, 4.4.0.Alpha1 Reporter: Nick Boldt Did some digging into the https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/jbds-dist-diff tool and discovered that its doc is not entirely straightforward. Also, it doesn't support headless JBDS installs, so it needs human bootstrapping. I propose making it support headless installs so it's more easily scriptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 14:05:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 5 Oct 2015 14:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20914) make jbds-dist-diff more user-friendly and scriptable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115161#comment-13115161 ] Nick Boldt commented on JBIDE-20914: ------------------------------------ {code} $? ./jbds-dist-diff.sh ~/tmp/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone.jar ~/tmp/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar [INFO] Install /home/nboldt/tmp/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone.jar into /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone real 1m57.235s user 2m37.254s sys 0m26.206s [INFO] Installed in /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone [INFO] Install /home/nboldt/tmp/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar into /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone real 1m56.286s user 2m33.083s sys 0m27.052s [INFO] Installed in /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone BUILD FAILED /home/nboldt/truu/jbdevstudio-qa/jbds-dist-diff/diff.xml:10: Unexpected differences were found or expected differences were not found Total time: 11 seconds real 0m11.890s user 0m16.530s sys 0m2.523s [INFO] Logs are in /tmp/tmp.bStU70UhlX: [INFO] * /tmp/tmp.bStU70UhlX/old_dir_file_list.log.txt [INFO] * /tmp/tmp.bStU70UhlX/new_dir_file_list.log.txt [INFO] * /tmp/tmp.bStU70UhlX/dist-diff.log.txt [INFO] * /tmp/tmp.bStU70UhlX/dist-diff-grepped-no-manifests.log.txt [INFO] * /tmp/tmp.bStU70UhlX/dist-diff-grepped-no-signatures.log.txt {code} -- PR: https://github.com/jbdevstudio/jbdevstudio-qa/pull/82 > make jbds-dist-diff more user-friendly and scriptable > ----------------------------------------------------- > > Key: JBIDE-20914 > URL: https://issues.jboss.org/browse/JBIDE-20914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR2, 4.4.0.Alpha1 > Reporter: Nick Boldt > > Did some digging into the https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/jbds-dist-diff tool and discovered that its doc is not entirely straightforward. > Also, it doesn't support headless JBDS installs, so it needs human bootstrapping. > I propose making it support headless installs so it's more easily scriptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:01:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 5 Oct 2015 15:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-504: ----------------------------- Attachment: disc-jbdsis.png disc-jbdsis-ea.png disc-jbtis-ea.png disc-jbtis.png > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:02:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 5 Oct 2015 15:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115181#comment-13115181 ] Paul Leacu commented on JBTIS-504: ---------------------------------- This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !disc-jbtis.png|thumbnail! !disc-jbtis-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:08:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 5 Oct 2015 15:08:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115183#comment-13115183 ] Alexey Kazakov commented on JBTIS-504: -------------------------------------- JBT looks good to me. JBDS message is a little bit long so it's cut. But anyway. It's much better now. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:19:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 5 Oct 2015 15:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115188#comment-13115188 ] Nick Boldt commented on JBTIS-504: ---------------------------------- Why not reuse the connector ID from the NA one as the connector ID for the first one that becomes available? Then it should disappear, along with its NA category. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:21:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 5 Oct 2015 15:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115190#comment-13115190 ] Len DiMaggio commented on JBTIS-504: ------------------------------------ So, if I understand Paul's suggestion, we'll have a single non-selectable note in place of the warning messages for the first several/many messages informing the user that some selections are only available through early access. That's a much better solution! > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:24:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 5 Oct 2015 15:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-504: ----------------------------- Attachment: jbtis-disc-ea.png jbtis-disc.png > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:26:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 5 Oct 2015 15:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115181#comment-13115181 ] Paul Leacu edited comment on JBTIS-504 at 10/5/15 3:25 PM: ----------------------------------------------------------- This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. was (Author: pleacu): This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !disc-jbtis.png|thumbnail! !disc-jbtis-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:27:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 5 Oct 2015 15:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115181#comment-13115181 ] Paul Leacu edited comment on JBTIS-504 at 10/5/15 3:26 PM: ----------------------------------------------------------- This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. JBDSIS Discovery: !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! JBTIS Discovery: !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. was (Author: pleacu): This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:33:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 5 Oct 2015 15:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115181#comment-13115181 ] Paul Leacu edited comment on JBTIS-504 at 10/5/15 3:32 PM: ----------------------------------------------------------- This proposal attempts to address two issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as 'not available' from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. JBDSIS Discovery: !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! JBTIS Discovery: !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. was (Author: pleacu): This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. JBDSIS Discovery: !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! JBTIS Discovery: !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 15:52:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 5 Oct 2015 15:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115206#comment-13115206 ] Max Rydahl Andersen commented on JBIDE-20912: --------------------------------------------- okey, so this work as expected. LiveReload.js is now forced into the web page so any setting in either browser or livereload will have zero effect. The livereload injected is not the livereload browsersim is reacting to. They just in this case have the same file name - it could just as well be something else than livereload that got injected. > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 16:40:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Mon, 5 Oct 2015 16:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20795: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 16:44:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Mon, 5 Oct 2015 16:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115218#comment-13115218 ] Snjezana Peco commented on JBIDE-20795: --------------------------------------- I have fixed the marker position. Eclipse already logs an exception when starting in the debug mode (using the -debug option). Please reopen the jira if you think we always have to log it. > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 16:58:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 5 Oct 2015 16:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115222#comment-13115222 ] Paul Leacu commented on JBTIS-504: ---------------------------------- Hey [~nickboldt] - your suggestion almost works. I reused the fuse tooling connector ID for the generic ID on the released side (the NA one). The NA connector disappeared as soon as I checked the 'Enable Early Access' which is great. After I installed all of the EA components and rebooted it returned. Definitely better... > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 21:58:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Mon, 5 Oct 2015 21:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115247#comment-13115247 ] Fred Bricon commented on JBIDE-20884: ------------------------------------- [~mhusnain], [~supriya.bharadwaj] wanna review do a quick review of https://github.com/jbosstools/jbosstools-website/pull/512 pretty please? > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22openshift%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 21:59:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Mon, 5 Oct 2015 21:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115247#comment-13115247 ] Fred Bricon edited comment on JBIDE-20884 at 10/5/15 9:58 PM: -------------------------------------------------------------- [~mhusnain], [~supriya.bharadwaj] wanna review do a quick review of https://github.com/jbosstools/jbosstools-website/pull/512 pretty please? Rendered page: https://github.com/fbricon/jbosstools-website/blob/os3-nn-430Final/documentation/whatsnew/openshift/openshift-news-3.0.0.Final.adoc was (Author: fbricon): [~mhusnain], [~supriya.bharadwaj] wanna review do a quick review of https://github.com/jbosstools/jbosstools-website/pull/512 pretty please? > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22openshift%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 23:55:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 5 Oct 2015 23:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115249#comment-13115249 ] Misha Ali commented on JBIDE-20884: ----------------------------------- Done, two minor typos, otherwise looks good. :) > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new -news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy+and+component+in+%28%22openshift%22%29] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 00:13:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Tue, 6 Oct 2015 00:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20708) tools.jboss.org/features: Add Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115251#comment-13115251 ] Misha Ali commented on JBIDE-20708: ----------------------------------- Done, added comments. Two minor typos, otherwise looks good! > tools.jboss.org/features: Add Docker > ------------------------------------ > > Key: JBIDE-20708 > URL: https://issues.jboss.org/browse/JBIDE-20708 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > We should add Docker to tools.jboss.org/features -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 01:32:00 2015 From: issues at jboss.org (Viacheslav Kabanovich (JIRA)) Date: Tue, 6 Oct 2015 01:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20910) XLabelProvider$RootWrapper memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115255#comment-13115255 ] Viacheslav Kabanovich commented on JBIDE-20910: ----------------------------------------------- I suspect an upstream issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=479098 > XLabelProvider$RootWrapper memory leak > -------------------------------------- > > Key: JBIDE-20910 > URL: https://issues.jboss.org/browse/JBIDE-20910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > I see amount of XLabelProvider$RootWrapper instances just raising in numbers when importing/deleting projects -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 02:52:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Tue, 6 Oct 2015 02:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115262#comment-13115262 ] Misha Ali commented on TOOLSDOC-683: ------------------------------------ Fixed and published for GA: https://access.redhat.com/articles/427493 Assuming that's all we needed to do, can someone from QE review and resolve this as acked? > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:13:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Tue, 6 Oct 2015 04:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) LiveReload is not disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115276#comment-13115276 ] Vlado Pakan commented on JBIDE-20912: ------------------------------------- It's not user friendly. User disables LiveReload but displayed page is still refreshed when page is updated and that is at least confusing. Disabling LiveReload extension in chrome with page opened via 'Show In' > 'Web Browser via LiveReolad Server' context menu of server view turns off refreshing of displayed page after page is updated on the file system so as a user I expect the same from BrowserSim. > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:20:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 6 Oct 2015 04:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj resolved TOOLSDOC-684. ---------------------------------------- Resolution: Done Doc published at: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio/9.0/html/Install_Red_Hat_JBoss_Developer_Studio/index.html > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:23:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Tue, 6 Oct 2015 04:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload In-Reply-To: References: Message-ID: Vlado Pakan created JBIDE-20915: ----------------------------------- Summary: HTML Page is not refreshed after page is changed in web browser with enabled LiveReload Key: JBIDE-20915 URL: https://issues.jboss.org/browse/JBIDE-20915 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.3.0.CR2 Environment: JBDS 9.0.0.GA-v20150925-1252-B116 Reporter: Vlado Pakan Priority: Critical 1. Import HTML 5 project from JBoss Central 2. Run it on server 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' ASSERT: index.html page is opened in system web browser 4. Make some changes to opened page and save them. ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. Repeat step 4. couple of times ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:27:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 6 Oct 2015 04:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-603) Openshift: Document how to push changes to an existing OS Project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj updated TOOLSDOC-603: --------------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT > Openshift: Document how to push changes to an existing OS Project > ----------------------------------------------------------------- > > Key: TOOLSDOC-603 > URL: https://issues.jboss.org/browse/TOOLSDOC-603 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Priority: Minor > Labels: openshift > Fix For: 4.3.0.Final > > > Document this use case: > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:27:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 6 Oct 2015 04:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj updated TOOLSDOC-307: --------------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:29:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 6 Oct 2015 04:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-603) Openshift: Document how to push changes to an existing OS Project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj reassigned TOOLSDOC-603: ------------------------------------------ Assignee: Supriya Bharadwaj (was: Misha Ali) > Openshift: Document how to push changes to an existing OS Project > ----------------------------------------------------------------- > > Key: TOOLSDOC-603 > URL: https://issues.jboss.org/browse/TOOLSDOC-603 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: openshift > Fix For: 4.3.0.Final > > > Document this use case: > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:52:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Tue, 6 Oct 2015 04:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115293#comment-13115293 ] Martin Malina commented on JBDS-3446: ------------------------------------- I recently came across a scenario where this feature would help. We have a script to compare two versions of JBDS for diffs. Nick improved the tool to support automated installation of JBDS from installer jar, but it currently doesn't work for me on Mac, because the default path is /Applications/jbdevstudio which fails on permissions. So it would be very useful to be able to specify the target destination on the command line. > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 10.x > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:52:00 2015 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Tue, 6 Oct 2015 04:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19684) Integrate Weld Prob into CDI Tools In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115294#comment-13115294 ] Martin Kouba commented on JBIDE-19684: -------------------------------------- FYI It's also possible to use JMX, i.e. if [JMX support is enabled|http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode] all the JSON data are available through a MXBean of name {{org.jboss.weld.probe:type=JsonData,context=ID}} where ID should be replaced with an idenfitier of an application. > Integrate Weld Prob into CDI Tools > ---------------------------------- > > Key: JBIDE-19684 > URL: https://issues.jboss.org/browse/JBIDE-19684 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi-extensions > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > *Blogs:* > http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html > https://developer.jboss.org/people/mkouba/blog/2015/02/05/weld-probe--inspect-your-cdi-application-at-runtime > *Live demo:* http://probe-weld.itos.redhat.com/weld-numberguess/weld-probe > *GitHub:* https://github.com/weld/core/tree/master/probe -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 05:16:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Tue, 6 Oct 2015 05:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20914) make jbds-dist-diff more user-friendly and scriptable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115303#comment-13115303 ] Martin Malina commented on JBIDE-20914: --------------------------------------- Thanks, [~nickboldt], for the effort. It didn't work out of the box for me on Mac, so I fixed it here: https://github.com/jbdevstudio/jbdevstudio-qa/pull/83 . (I wish github allowed me to contribute to your PR instead.) So I propose to use that PR. It works for me except the automated installation. > make jbds-dist-diff more user-friendly and scriptable > ----------------------------------------------------- > > Key: JBIDE-20914 > URL: https://issues.jboss.org/browse/JBIDE-20914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR2, 4.4.0.Alpha1 > Reporter: Nick Boldt > > Did some digging into the https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/jbds-dist-diff tool and discovered that its doc is not entirely straightforward. > Also, it doesn't support headless JBDS installs, so it needs human bootstrapping. > I propose making it support headless installs so it's more easily scriptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 05:22:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Tue, 6 Oct 2015 05:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina resolved TOOLSDOC-683. ------------------------------------ Resolution: Done Thanks, [~mhusnain], it's correct. > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 05:22:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Tue, 6 Oct 2015 05:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed TOOLSDOC-683. ---------------------------------- Closing. > Rel notes for 4.3.0 should list supported Codova versions > --------------------------------------------------------- > > Key: TOOLSDOC-683 > URL: https://issues.jboss.org/browse/TOOLSDOC-683 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: Configurations, Supported > Fix For: 4.3.0.Final > > > Related to: JBIDE-20836 > The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:17:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 6 Oct 2015 06:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-20916: ------------------------------------------- Summary: importing jbosstools-website results in error Key: JBIDE-20916 URL: https://issues.jboss.org/browse/JBIDE-20916 Project: Tools (JBoss Tools) Issue Type: Bug Components: easymport Reporter: Max Rydahl Andersen use import nested of jbosstools-website result in progress dialog showing error saying: {quote} bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin {quote} No additional info provided. (note: this happened on second import so it might be when .project already there) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:17:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Tue, 6 Oct 2015 06:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria reassigned JBIDE-20916: -------------------------------------- Assignee: Mickael Istria > importing jbosstools-website results in error > --------------------------------------------- > > Key: JBIDE-20916 > URL: https://issues.jboss.org/browse/JBIDE-20916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > use import nested of jbosstools-website result in progress dialog showing error saying: > {quote} > bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin > {quote} > No additional info provided. > (note: this happened on second import so it might be when .project already there) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:18:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 6 Oct 2015 06:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115335#comment-13115335 ] Max Rydahl Andersen commented on JBIDE-20916: --------------------------------------------- It seem to not log all the time. Tried a few times with no errors in log (still error dialog) but I now see this one in logs: {quote} org.eclipse.ui.internal.wizards.datatransfer.CouldNotImportProjectException: Could not import project located at /Users/max/Documents/workspace-centraltest at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.toExistingOrNewProject(EasymportJob.java:365) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:101) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.eclipse.core.internal.resources.ResourceException: Invalid project description. at org.eclipse.core.internal.resources.Project.checkDescription(Project.java:168) at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:52) at org.eclipse.core.internal.resources.Project.create(Project.java:268) at org.eclipse.core.internal.resources.Project.create(Project.java:252) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.createOrImportProject(EasymportJob.java:401) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.toExistingOrNewProject(EasymportJob.java:353) ... 2 more {quote} > importing jbosstools-website results in error > --------------------------------------------- > > Key: JBIDE-20916 > URL: https://issues.jboss.org/browse/JBIDE-20916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > use import nested of jbosstools-website result in progress dialog showing error saying: > {quote} > bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin > {quote} > No additional info provided. > (note: this happened on second import so it might be when .project already there) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:21:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Tue, 6 Oct 2015 06:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect if In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20912: -------------------------------- Summary: Enable / Disable LiveReload settings have no effect if (was: LiveReload is not disabled) > Enable / Disable LiveReload settings have no effect if > ------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:22:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Tue, 6 Oct 2015 06:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115337#comment-13115337 ] Mickael Istria commented on JBIDE-20916: ---------------------------------------- The bin/ folder was created by an earlier issue: this project was once imported as a Java one, and JDT created a bin folder. When importing (again) the project wasn't detected as a Java project, so bin/ was crawled (it's excluded for Java projects) and it is most likely that the bin/ folder contains a .project file that has same name as jbosstools-website. Import is complaining because it cannot import bin/ as jbosstools-website when there is already a jbosstools-website. > importing jbosstools-website results in error > --------------------------------------------- > > Key: JBIDE-20916 > URL: https://issues.jboss.org/browse/JBIDE-20916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > use import nested of jbosstools-website result in progress dialog showing error saying: > {quote} > bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin > {quote} > No additional info provided. > (note: this happened on second import so it might be when .project already there) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:22:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Tue, 6 Oct 2015 06:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for urls with In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20912: -------------------------------- Summary: Enable / Disable LiveReload settings have no effect for urls with (was: Enable / Disable LiveReload settings have no effect if ) > Enable / Disable LiveReload settings have no effect for urls with > ------------------------------------------------------------------ > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:22:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Tue, 6 Oct 2015 06:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20912: -------------------------------- Summary: Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js (was: Enable / Disable LiveReload settings have no effect for urls with ) > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:28:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 6 Oct 2015 06:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115341#comment-13115341 ] Max Rydahl Andersen commented on JBIDE-20912: --------------------------------------------- No, the browser live reload extension have no impact on the javascript already injected. When I open a page with live reload included firefox live reload plugin does not show it is on - but it still live reloads. Again, imagine if we just injected something called "dynamic-reload.js" instead - would you also expect the LiveReload extensions to be able to detect it ? IMO, no. and just because we inject javascript of the same name should not imply that live reload extensions to any browser can dynamically figure it out. > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:43:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 6 Oct 2015 06:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-670) Add a pre-req in the Create Your First Hybrid Mobile App how-to in community In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115343#comment-13115343 ] Supriya Bharadwaj commented on TOOLSDOC-670: -------------------------------------------- Content added and document published at: Customer Portal: https://access.redhat.com/articles/1518153 Community: http://tools.jboss.org/documentation/howto/hmt_firstapp.html > Add a pre-req in the Create Your First Hybrid Mobile App how-to in community > ---------------------------------------------------------------------------- > > Key: TOOLSDOC-670 > URL: https://issues.jboss.org/browse/TOOLSDOC-670 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Priority: Minor > > Add the Enable the JBoss Hybrid Mobile Tools + CordovaSim Feature pre-req from https://access.redhat.com/articles/1518153 to the pre-reqs section in Create Your First Hybrid Mobile App how-to -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:43:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 6 Oct 2015 06:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-670) Add a pre-req in the Create Your First Hybrid Mobile App how-to in community In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj resolved TOOLSDOC-670. ---------------------------------------- Resolution: Done > Add a pre-req in the Create Your First Hybrid Mobile App how-to in community > ---------------------------------------------------------------------------- > > Key: TOOLSDOC-670 > URL: https://issues.jboss.org/browse/TOOLSDOC-670 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Priority: Minor > > Add the Enable the JBoss Hybrid Mobile Tools + CordovaSim Feature pre-req from https://access.redhat.com/articles/1518153 to the pre-reqs section in Create Your First Hybrid Mobile App how-to -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:49:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 6 Oct 2015 06:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-677) Review: Create and Monitor OS v3 Apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj resolved TOOLSDOC-677. ---------------------------------------- Resolution: Done Hi [~fbricon], I have incorporated your comments in the doc which is now live on the Portal and in the community. Therefore, resolving the JIRA. Portal: https://access.redhat.com/articles/1610503 Community: http://tools.jboss.org/documentation/howto/os3_startusing.html > Review: Create and Monitor OS v3 Apps > ------------------------------------- > > Key: TOOLSDOC-677 > URL: https://issues.jboss.org/browse/TOOLSDOC-677 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Can someone please review the article at: https://docs.google.com/document/d/1mevNqMkYVe41Lc_-NcfvYC8lcbD-FFJqoSZaxUzr7-s/edit#heading=h.lqc95xrzxc31 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 07:10:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Tue, 6 Oct 2015 07:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20917) Wrong default name for java ee 7 archetypes In-Reply-To: References: Message-ID: Radim Hopp created JBIDE-20917: ---------------------------------- Summary: Wrong default name for java ee 7 archetypes Key: JBIDE-20917 URL: https://issues.jboss.org/browse/JBIDE-20917 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.3.0.CR1 Reporter: Radim Hopp Priority: Minor It looks like if the archetype does not provide default name, package etc. Some default values are used (for EAR project it is "jboss-javaee6-multi"). This name is not right at least in situation, when JavaEE7 archetype is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 07:35:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Tue, 6 Oct 2015 07:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.x) > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: help_wanted, openshift_v3 > Fix For: 4.3.1.Final > > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png, edit-connection-4.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 07:36:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Tue, 6 Oct 2015 07:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Fix Version/s: 4.3.x > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: help_wanted, openshift_v3 > Fix For: 4.3.x > > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png, edit-connection-4.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 07:36:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Tue, 6 Oct 2015 07:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Fix Version/s: (was: 4.3.1.Final) > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: help_wanted, openshift_v3 > Fix For: 4.3.x > > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png, edit-connection-4.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 07:59:01 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 6 Oct 2015 07:59:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20917) Wrong default name for java ee 7 archetypes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen reassigned JBIDE-20917: ------------------------------------------- Assignee: Fred Bricon > Wrong default name for java ee 7 archetypes > ------------------------------------------- > > Key: JBIDE-20917 > URL: https://issues.jboss.org/browse/JBIDE-20917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Minor > > It looks like if the archetype does not provide default name, package etc. Some default values are used (for EAR project it is "jboss-javaee6-multi"). This name is not right at least in situation, when JavaEE7 archetype is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 08:00:03 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 6 Oct 2015 08:00:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20917) Wrong default name for java ee 7 archetypes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115380#comment-13115380 ] Max Rydahl Andersen commented on JBIDE-20917: --------------------------------------------- [~fbricon] is this an archetype issue or in our metadata ? > Wrong default name for java ee 7 archetypes > ------------------------------------------- > > Key: JBIDE-20917 > URL: https://issues.jboss.org/browse/JBIDE-20917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Minor > > It looks like if the archetype does not provide default name, package etc. Some default values are used (for EAR project it is "jboss-javaee6-multi"). This name is not right at least in situation, when JavaEE7 archetype is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 08:37:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 08:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20910) XLabelProvider$RootWrapper memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20910: ----------------------------------- Component/s: upstream > XLabelProvider$RootWrapper memory leak > -------------------------------------- > > Key: JBIDE-20910 > URL: https://issues.jboss.org/browse/JBIDE-20910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > I see amount of XLabelProvider$RootWrapper instances just raising in numbers when importing/deleting projects -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 08:37:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 08:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20910) XLabelProvider$RootWrapper memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20910: ----------------------------------- Component/s: (was: common/jst/core) > XLabelProvider$RootWrapper memory leak > -------------------------------------- > > Key: JBIDE-20910 > URL: https://issues.jboss.org/browse/JBIDE-20910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > I see amount of XLabelProvider$RootWrapper instances just raising in numbers when importing/deleting projects -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 08:52:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 6 Oct 2015 08:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20917) Wrong default name for java ee 7 archetypes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115430#comment-13115430 ] Fred Bricon commented on JBIDE-20917: ------------------------------------- It's a metadata issue. I need to investigate > Wrong default name for java ee 7 archetypes > ------------------------------------------- > > Key: JBIDE-20917 > URL: https://issues.jboss.org/browse/JBIDE-20917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Minor > > It looks like if the archetype does not provide default name, package etc. Some default values are used (for EAR project it is "jboss-javaee6-multi"). This name is not right at least in situation, when JavaEE7 archetype is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 09:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20915: -------------------------------------- Assignee: Xavier Coulon > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:26:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 09:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20915: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20912. ------------------------------------ Resolution: Rejected I'm rejecting the JIRA. Maybe it's not ideal from user experience point of view but this is how it works and we don't have better idea how we could improve it. > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:45:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 09:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115467#comment-13115467 ] Nick Boldt commented on JBDS-3446: ---------------------------------- For now, would a workaround for JBIDE-20914 (making the jbds-dist-diff script support headless install) be to create a /Applications/jbdevstudio folder with the correct permissions? Then we could tweak the script to move the CONTENTS of the folder rather than the whole folder. Or, what if the jbds-dist-diff script creates the folder and sets the correct write perms before doing the console install? Or could the script detect the OS and if OSX, prompt the user to run the install as root? Of course, the best / most flexible solution would be to be able to set the install path via commandline (because then we could push into /tmp/ instead of ~/ or /Applications/) but would any of the above workarounds work in the short-term? > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 10.x > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:51:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 09:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20914) make jbds-dist-diff more user-friendly and scriptable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20914: ------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-qa/pull/83 (was: https://github.com/jbdevstudio/jbdevstudio-qa/pull/82) > make jbds-dist-diff more user-friendly and scriptable > ----------------------------------------------------- > > Key: JBIDE-20914 > URL: https://issues.jboss.org/browse/JBIDE-20914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR2, 4.4.0.Alpha1 > Reporter: Nick Boldt > > Did some digging into the https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/jbds-dist-diff tool and discovered that its doc is not entirely straightforward. > Also, it doesn't support headless JBDS installs, so it needs human bootstrapping. > I propose making it support headless installs so it's more easily scriptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:04:33 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Tue, 6 Oct 2015 10:04:33 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20914) make jbds-dist-diff more user-friendly and scriptable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed JBIDE-20914. --------------------------------- Fix Version/s: 4.3.0.Final Assignee: Nick Boldt Resolution: Done PR merged. Done. > make jbds-dist-diff more user-friendly and scriptable > ----------------------------------------------------- > > Key: JBIDE-20914 > URL: https://issues.jboss.org/browse/JBIDE-20914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Did some digging into the https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/jbds-dist-diff tool and discovered that its doc is not entirely straightforward. > Also, it doesn't support headless JBDS installs, so it needs human bootstrapping. > I propose making it support headless installs so it's more easily scriptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:30:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Tue, 6 Oct 2015 10:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20909) Mistype errors in General What's New in 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlado Pakan closed JBIDE-20909. ------------------------------- Verified > Mistype errors in General What's New in 4.3.0.Final > --------------------------------------------------- > > Key: JBIDE-20909 > URL: https://issues.jboss.org/browse/JBIDE-20909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Final > Environment: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html#general > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.3.0.Final > > > * 'JBoss Tools new integrate new' -> 'JBoss Tools now integrate new' > * 'best inside ythe IDE' -> 'best inside the IDE' > * 'user isn?t required how to import' -> 'user isn?t required to know how to import' -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:34:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Tue, 6 Oct 2015 10:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20696) tools.jboss.org/features: Add HTML5 Palette In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlado Pakan closed JBIDE-20696. ------------------------------- Verified > tools.jboss.org/features: Add HTML5 Palette > ------------------------------------------- > > Key: JBIDE-20696 > URL: https://issues.jboss.org/browse/JBIDE-20696 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.Final > > > We should add HTML5 Palette feature to the [HTML5/JS/CSS|http://tools.jboss.org/features/html5.html] page. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:38:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Tue, 6 Oct 2015 10:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115520#comment-13115520 ] Martin Malina commented on JBDS-3446: ------------------------------------- [~nickboldt], yes, running the script with sudo will do the trick for now (as long as I trust it not to do anything nasty ;) ). > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 10.x > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:39:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 10:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20876) Create New and Noteworthy for 4.3.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20876. ------------------------------------ Resolution: Done > Create New and Noteworthy for 4.3.0.Final > ----------------------------------------- > > Key: JBIDE-20876 > URL: https://issues.jboss.org/browse/JBIDE-20876 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.3.0.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Final%22%29%29+AND+resolution+%3D+Done+AND+labels+%3D+new_and_noteworthy] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:41:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 10:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20708) tools.jboss.org/features: Add Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20708: ------------------------------- Component/s: website > tools.jboss.org/features: Add Docker > ------------------------------------ > > Key: JBIDE-20708 > URL: https://issues.jboss.org/browse/JBIDE-20708 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, website > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > We should add Docker to tools.jboss.org/features -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:42:01 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Tue, 6 Oct 2015 10:42:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Migrate browsersim and cordovasim to jetty v 9.3.2 In-Reply-To: References: Message-ID: Konstantin Marmalyukov created JBIDE-20918: ---------------------------------------------- Summary: Migrate browsersim and cordovasim to jetty v 9.3.2 Key: JBIDE-20918 URL: https://issues.jboss.org/browse/JBIDE-20918 Project: Tools (JBoss Tools) Issue Type: Task Components: browsersim, cordovasim Affects Versions: 4.4.0.Alpha1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:52:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 10:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20600) document how to use Deploy to OpenShift (Docker integration) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20600: -------------------------------------- Assignee: Fred Bricon (was: Jeff Cantrill) > document how to use Deploy to OpenShift (Docker integration) > ------------------------------------------------------------ > > Key: JBIDE-20600 > URL: https://issues.jboss.org/browse/JBIDE-20600 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Final > > > Trying to use the Deploy to OpenShift dialog I found a few issues and i'm a bit stuck figuring out how it works. > What I did was trying to just take jboss/wildfly:latest and deploy to openshift. > First off, the first page of Deploy to openshift wont let me create a connection or project so I have as a user to have done that *before* starting the dialog. > Once I have done that the dialog is asking for a lot of questions but very little hints about what they are. > One example is "Add Route" on services ports page - that page can have multiple services so which does "Add Route" refer to and should it not need to know which port needed to use ? > But worst issue is that once all that is filled out then I do not seem to be able to get any logs or info on why wildfly is not started. > neither in webconsole nor in eclipse views. > Should there not be access to some console logs or similar to things created by a project ? > anyway - long description to point out we need some docs on how to actually use this if we cannot fix the UI before GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 10:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-18820: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.0.Final) > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.1.Final > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 10:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20693) Add new features for tools.jboss.org/features/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20693: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.0.Final) > Add new features for tools.jboss.org/features/ > ---------------------------------------------- > > Key: JBIDE-20693 > URL: https://issues.jboss.org/browse/JBIDE-20693 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:13:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 6 Oct 2015 11:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115544#comment-13115544 ] Max Rydahl Andersen commented on JBIDE-20912: --------------------------------------------- Your changes will make browsersim work different from how the normal browsers works. I think that is a slippery slope. > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:20:00 2015 From: issues at jboss.org (Vikram Jammula (JIRA)) Date: Tue, 6 Oct 2015 11:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115552#comment-13115552 ] Vikram Jammula commented on JBDS-3533: -------------------------------------- [~akazakov] I have installed 8.1 JBDS and everything works fine. Thanks [~mickael_istria] for your help. > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Denis Golovin > Priority: Minor > Fix For: 9.x > > Attachments: check Updates.png, security.jpg > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:31:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 11:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115568#comment-13115568 ] Nick Boldt commented on JBTIS-504: ---------------------------------- [~pleacu] Please document here which URLs will contain your latest plugin jars. Will they be Alpha2? Alpha3? /staging/ ? /snapshots/ ? Also, please ensure that the site's plugins/ folder only contains 2 plugins, not 18. eg., http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-stack/discovery/4.3.0.Alpha2/plugins/ (good) http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/plugins/ (bad - too many plugins!) > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:34:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Tue, 6 Oct 2015 11:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115571#comment-13115571 ] Vlado Pakan commented on JBIDE-20912: ------------------------------------- It works exactly as I want with Google Chrome which is one of mostly used web browsers: When user clicks on LiveReload extension icon in Chrome and disables the LiveReload page is not refreshed after changes are saved to page. I don't understand problem with removing proper javascript file from displayed web page. We are injecting it when LvieReload is enabled in BrowserSim so why it's such a big problem to remove it especially when Chrome is able to handle it somehow. We can also alter page send from server to inform BrowserSim that LiveReload javascript was injected to the page by our tooling so it's save to remove it I guess. However I'm ok with rejecting this issue in case it's complicated even I don't see why it's so. > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:41:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 6 Oct 2015 11:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115577#comment-13115577 ] Max Rydahl Andersen commented on JBIDE-20912: --------------------------------------------- [~vpakan] you tell me how chrome does it then we can talk ;) for now you are suggesting the browser looks for code in all html pages for a snippet that might or might not be injected by our tools. > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:45:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 11:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBDS-3533. -------------------------------- Fix Version/s: 8.1.0.GA (was: 9.x) Resolution: Duplicate Issue > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.1.0.GA > > Attachments: check Updates.png, security.jpg > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:57:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Tue, 6 Oct 2015 11:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3244: -------------------------------- Fix Version/s: (was: 9.0.0.GA) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 11:57:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Tue, 6 Oct 2015 11:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3244: -------------------------------- Fix Version/s: 9.0.0.GA > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:00:01 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Tue, 6 Oct 2015 12:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115584#comment-13115584 ] Vlado Pakan commented on JBIDE-20912: ------------------------------------- I don't know how Chrome is doing it but it works and I'm not able to say how much time is needed to find it out or if it's even possible to find out.. I don't know how server is injecting LiveReload javascript to the page so I can't say how difficult would be to find it and remove it on BrowserSim side. > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:01:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Tue, 6 Oct 2015 12:01:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3244: -------------------------------- Fix Version/s: (was: 9.0.0.GA) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:01:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 6 Oct 2015 12:01:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3244: ----------------------------- > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:01:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Tue, 6 Oct 2015 12:01:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3244: -------------------------------- Target Release: 10.0.0.GA (was: 9.0.0.GA) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:01:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 6 Oct 2015 12:01:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3244: -------------------------------- > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:02:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Tue, 6 Oct 2015 12:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3244: -------------------------------- Fix Version/s: 10.0.0.GA > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:02:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3244: --------------------------------- Fix Version/s: 9.0.1.GA 10.0.0.Alpha1 (was: 10.0.0.GA) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3244: --------------------------------- Fix Version/s: 10.0.0.GA (was: 10.0.0.Alpha1) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:51:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3257) Basic FeedHenry Support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3257: --------------------------------- Fix Version/s: 10.0.0.GA (was: 9.0.0.GA) (was: 8.1.0.GA) > Basic FeedHenry Support > ----------------------- > > Key: JBDS-3257 > URL: https://issues.jboss.org/browse/JBDS-3257 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, requirements > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 10.0.0.GA > > > as feedhenry user I would like to be able to easily import my existing feedhenry application into developer studio and allow me to edit and commit code back to feedhenry. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:52:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3245: --------------------------------- Fix Version/s: 9.0.1.GA 10.0.0.GA (was: 9.0.0.GA) > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3247) Hybrid Mobile Tooling covering base Apache Cordova In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3247: --------------------------------- Fix Version/s: 10.0.0.GA (was: 9.0.0.GA) > Hybrid Mobile Tooling covering base Apache Cordova > -------------------------------------------------- > > Key: JBDS-3247 > URL: https://issues.jboss.org/browse/JBDS-3247 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, cordovasim, requirements > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:54:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3246) As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBDS-3246. -------------------------------- Resolution: Done > As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3246 > URL: https://issues.jboss.org/browse/JBDS-3246 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 9.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3249: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) > As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps > ------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3249 > URL: https://issues.jboss.org/browse/JBDS-3249 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer, integration-platform, requirements, updatesite > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > > Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find. > Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276) > From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:56:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18722) Fixing Eclipse/Neon (+Mars SR2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-18722: ----------------------------------- Fix Version/s: 4.4.0.Final > Fixing Eclipse/Neon (+Mars SR2) > ------------------------------- > > Key: JBIDE-18722 > URL: https://issues.jboss.org/browse/JBIDE-18722 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.1.Final, 4.4.0.Final > > > "container" issue for issues related to fixes important to get into Luna. > Please link your Eclipse/Mars issue to this one instead of using subtasks (edit this description). > Current open WTP bugs with patches waiting to be applied (copy from original issue without fixed): > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: Future > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 show in console. target: none > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=318670 - [Workbench] Not all settings copied when switching workspace and "Copy settings" marked -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: Alexey Kazakov created JBDS-3536: ------------------------------------ Summary: Target Platform Requirements for JBDS 10.0.0.GA Key: JBDS-3536 URL: https://issues.jboss.org/browse/JBDS-3536 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform Affects Versions: 9.0.0.Alpha1 Reporter: Nick Boldt Assignee: Len DiMaggio Priority: Blocker Fix For: 9.0.0.GA Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:59:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 6 Oct 2015 12:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3536: -------------------------------- > Target Platform Requirements for JBDS 10.0.0.GA > ----------------------------------------------- > > Key: JBDS-3536 > URL: https://issues.jboss.org/browse/JBDS-3536 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 9.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 12:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 12:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3536: --------------------------------- Affects Version/s: 10.0.0.Alpha1 (was: 9.0.0.Alpha1) > Target Platform Requirements for JBDS 10.0.0.GA > ----------------------------------------------- > > Key: JBDS-3536 > URL: https://issues.jboss.org/browse/JBDS-3536 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 9.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:01:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3536: --------------------------------- Epic Name: JBDS 10 Target Platform (was: JBDS 9 Target Platform) > Target Platform Requirements for JBDS 10.0.0.GA > ----------------------------------------------- > > Key: JBDS-3536 > URL: https://issues.jboss.org/browse/JBDS-3536 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 9.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:04:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 6 Oct 2015 13:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3510) Consider including Buildship in JBT/JBDS - add new connector to Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3510: ----------------------------- > Consider including Buildship in JBT/JBDS - add new connector to Central > ----------------------------------------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery > Affects Versions: 9.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3510) Consider including Buildship in JBT/JBDS - add new connector to Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3510: --------------------------------- Target Release: (was: 9.1.0.GA) > Consider including Buildship in JBT/JBDS - add new connector to Central > ----------------------------------------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery > Affects Versions: 9.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3510) Consider including Buildship in JBT/JBDS - add new connector to Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3510: --------------------------------- Fix Version/s: 10.x (was: 9.x) > Consider including Buildship in JBT/JBDS - add new connector to Central > ----------------------------------------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery > Affects Versions: 9.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:05:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3536: --------------------------------- Fix Version/s: 10.0.0.GA (was: 9.0.0.GA) > Target Platform Requirements for JBDS 10.0.0.GA > ----------------------------------------------- > > Key: JBDS-3536 > URL: https://issues.jboss.org/browse/JBDS-3536 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:05:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 6 Oct 2015 13:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3536: ----------------------------- > Target Platform Requirements for JBDS 10.0.0.GA > ----------------------------------------------- > > Key: JBDS-3536 > URL: https://issues.jboss.org/browse/JBDS-3536 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:05:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 6 Oct 2015 13:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3536: -------------------------------- > Target Platform Requirements for JBDS 10.0.0.GA > ----------------------------------------------- > > Key: JBDS-3536 > URL: https://issues.jboss.org/browse/JBDS-3536 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:05:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3536) Target Platform Requirements for JBDS 10.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3536: --------------------------------- Target Release: 10.0.0.GA (was: 9.0.0.GA) > Target Platform Requirements for JBDS 10.0.0.GA > ----------------------------------------------- > > Key: JBDS-3536 > URL: https://issues.jboss.org/browse/JBDS-3536 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:05:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3299) Target Platform Requirements for JBDS 9.0.0.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBDS-3299. ---------------------------------- Resolution: Done > Target Platform Requirements for JBDS 9.0.0.GA > ---------------------------------------------- > > Key: JBDS-3299 > URL: https://issues.jboss.org/browse/JBDS-3299 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 9.0.0.GA > > > Track changes to third party inclusions in JBDS 9 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:08:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115614#comment-13115614 ] Alexey Kazakov commented on JBDS-3516: -------------------------------------- {quote} I'd be glad to give a try to a more accurate explanation. However, where should I submit PRs ? {quote} [~mhusnain]? > Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] > ------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3516 > URL: https://issues.jboss.org/browse/JBDS-3516 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, documentation, updatesite > Affects Versions: 9.0.0.CR1 > Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100 > jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0.0.CR1-updatesite-central.zip > Reporter: Jan Richter > Assignee: Mickael Istria > Fix For: 9.0.0.GA > > > This is what comes up when I try to install everything from the central zip: > {noformat} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20917) Wrong default name for java ee 7 archetypes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20917: ----------------------------------- Priority: Major (was: Minor) > Wrong default name for java ee 7 archetypes > ------------------------------------------- > > Key: JBIDE-20917 > URL: https://issues.jboss.org/browse/JBIDE-20917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Fred Bricon > > It looks like if the archetype does not provide default name, package etc. Some default values are used (for EAR project it is "jboss-javaee6-multi"). This name is not right at least in situation, when JavaEE7 archetype is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:18:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:18:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3281) Screencasts: Git In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3281: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) I'm moving all these screencast issues to JBDS 9.0.1 because we don't have time to have it done by JBDS 9.0.0.GA release date. However I'm hopping [~mmalina] will have some free time after 9.0.0.GA release to finish this task right after JBDS 9 release. > Screencasts: Git > ---------------- > > Key: JBDS-3281 > URL: https://issues.jboss.org/browse/JBDS-3281 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, requirements > Reporter: Burr Sutter > Assignee: Martin Malina > Priority: Minor > Fix For: 9.0.1.GA > > > As a Java EE developer, new to Eclipse + Git, I need educational, 5 minute screencasts on the most common uses of Git inside of Eclipse. > Use cases include: > 1) as a new member of the team, just having only installed JBDS, I need to add an element to the project > assume a clone, add (or modify), commit, push workflow > a- Getting started as a new member of an existing git project (I need to clone a repo, import the project, insure my facets/Maven are set correctly) > b- navigate/browse an existing repository > c- git add - for a newly added class or file > d- git commit -a > e- git push > as a new member of the team, just having only installed JBDS, I need to resolve a pull request. > 2) other scenarios > - git init a current project that I have in my workspace (and should I move it outside of my workspace first) > - git checkout for a specific branch - getting Maven and Eclipse Facets to properly recognize my newly checked out branch -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:18:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:18:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3280) Screencasts: Java EE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3280: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) I'm moving all these screencast issues to JBDS 9.0.1 because we don't have time to have it done by JBDS 9.0.0.GA release date. However I'm hopping [~mmalina] will have some free time after 9.0.0.GA release to finish this task right after JBDS 9 release. > Screencasts: Java EE > -------------------- > > Key: JBDS-3280 > URL: https://issues.jboss.org/browse/JBDS-3280 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, requirements > Reporter: Burr Sutter > Assignee: Martin Malina > Priority: Minor > Fix For: 9.0.1.GA > > > As a new Eclipse+Java EE developer, I need educational screencasts, around 5 minutes each that educate me on a specific Java EE development capabilities of JBDS. > Use cases include: > - JPA - how to add one, content-assist, relationships > - database reverse engineering via DTP vs Forge > - JAX-RS: creation of new endpoints, content-assist, tester - including the GET/POST/PUT/DELETE with JSON payloads > - JAX-WS: creation of new endpoints, content-assist, tester > - CDI special features > - Servlets > - JSF > - deployment to localhost EAP > - deployment to remove EAP -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:18:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:18:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3279) Screencasts: Maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3279: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) I'm moving all these screencast issues to JBDS 9.0.1 because we don't have time to have it done by JBDS 9.0.0.GA release date. However I'm hopping [~mmalina] will have some free time after 9.0.0.GA release to finish this task right after JBDS 9 release. > Screencasts: Maven > ------------------ > > Key: JBDS-3279 > URL: https://issues.jboss.org/browse/JBDS-3279 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, maven, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Fix For: 9.0.1.GA > > > As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow. > Use cases include: > - creation of a new project and its pom.xml, with the pom.xml editor > - dependencies adds/removes > - Import maven projects - from a SVN or Git repo > - multi-module maven projects > - run on server > - package vs install > - update - the magic "update project" that helps get Eclipse and Maven back into agreement > - adjust profiles - address the Arquillian profile -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:18:06 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:18:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-2705: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) I'm moving all these screencast issues to JBDS 9.0.1 because we don't have time to have it done by JBDS 9.0.0.GA release date. However I'm hopping [~mmalina] will have some free time after 9.0.0.GA release to finish this task right after JBDS 9 release. > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 9.0.1.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:18:06 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:18:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3282: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) I'm moving all these screencast issues to JBDS 9.0.1 because we don't have time to have it done by JBDS 9.0.0.GA release date. However I'm hopping [~mmalina] will have some free time after 9.0.0.GA release to finish this task right after JBDS 9 release. > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.1.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:18:07 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:18:07 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3251) Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3251: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) I'm moving all these screencast issues to JBDS 9.0.1 because we don't have time to have it done by JBDS 9.0.0.GA release date. However I'm hopping [~mmalina] will have some free time after 9.0.0.GA release to finish this task right after JBDS 9 release. > Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3251 > URL: https://issues.jboss.org/browse/JBDS-3251 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: documentation, requirements > Reporter: Max Rydahl Andersen > Assignee: Martin Malina > Fix For: 9.0.1.GA > > > suggestions from F2F: > |Maven Top 10 Use Cases| Import, multi-module, run on server, package vs install, update, adjust profiles, dependencies adds/removes| > |Java EE Top 10 Use Cases JPA, db reveng, JAX-RS (including testing), CDI, content assist, Servlets, JSF, etc > HTML5/Hybrid Mobile| > |OpenShift v3| start, stop, deploy apps > |eGit Top Use Cases| -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:18:07 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 13:18:07 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3516: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) > Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] > ------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3516 > URL: https://issues.jboss.org/browse/JBDS-3516 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, documentation, updatesite > Affects Versions: 9.0.0.CR1 > Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100 > jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0.0.CR1-updatesite-central.zip > Reporter: Jan Richter > Assignee: Mickael Istria > Fix For: 9.0.1.GA > > > This is what comes up when I try to install everything from the central zip: > {noformat} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:54:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 13:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-2705: ----------------------------- Fix Version/s: 9.0.0.GA (was: 9.0.1.GA) > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 13:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 13:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2705) Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-2705: ----------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.0.GA) > Screencasts: update "JBoss Developer Studio X in 5 Minutes" to use JBDS 9 - http://vimeo.com/60064715 > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Labels: screencast > Fix For: 9.0.1.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 14:21:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 6 Oct 2015 14:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20917) Wrong default name for java ee 7 archetypes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-20917. --------------------------------- Fix Version/s: 4.3.0.Final Resolution: Done The fix was trivial, after all. The default project name is actually defined in the shared project-example descriptor. So I changed it to jboss-javaee-webapp for the webapp and to jboss-javaee-multi for the EAR project > Wrong default name for java ee 7 archetypes > ------------------------------------------- > > Key: JBIDE-20917 > URL: https://issues.jboss.org/browse/JBIDE-20917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.0.Final > > > It looks like if the archetype does not provide default name, package etc. Some default values are used (for EAR project it is "jboss-javaee6-multi"). This name is not right at least in situation, when JavaEE7 archetype is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 14:58:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Tue, 6 Oct 2015 14:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Migrate browsersim and cordovasim to jetty v 9.3.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20918: ------------------------------------------- Description: In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > Migrate browsersim and cordovasim to jetty v 9.3.2 > -------------------------------------------------- > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 15:44:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 15:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20708) tools.jboss.org/features: Add Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115670#comment-13115670 ] Nick Boldt commented on JBIDE-20708: ------------------------------------ Can this be pushed? Or is it waiting for JBT to be released? > tools.jboss.org/features: Add Docker > ------------------------------------ > > Key: JBIDE-20708 > URL: https://issues.jboss.org/browse/JBIDE-20708 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, website > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > We should add Docker to tools.jboss.org/features -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 16:52:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 6 Oct 2015 16:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20708) tools.jboss.org/features: Add Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115685#comment-13115685 ] Alexey Kazakov commented on JBIDE-20708: ---------------------------------------- We are waiting [~xcoulon] to update his PR (add some intro to the feature description). He is going to do it tomorrow's morning. I don't see any problem if you have this jira open for JBT 4.3.0.Final until tomorrow. Do you? > tools.jboss.org/features: Add Docker > ------------------------------------ > > Key: JBIDE-20708 > URL: https://issues.jboss.org/browse/JBIDE-20708 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, website > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > We should add Docker to tools.jboss.org/features -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 20:57:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 6 Oct 2015 20:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115702#comment-13115702 ] Paul Leacu commented on JBTIS-504: ---------------------------------- [~nickboldt] - The JBTIS development discovery is working. The plugin URLs can be found here: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/plugins http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins To test: {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2 \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess {code} Still working on devstudio discovery. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 20:58:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 6 Oct 2015 20:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115702#comment-13115702 ] Paul Leacu edited comment on JBTIS-504 at 10/6/15 8:57 PM: ----------------------------------------------------------- [~nickboldt] - The JBTIS development discovery is working. The plugin URLs can be found here: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/plugins http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins To test: {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2 \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess {code} Still working on devstudio discovery. was (Author: pleacu): [~nickboldt] - The JBTIS development discovery is working. The plugin URLs can be found here: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/plugins http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins To test: {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2 \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess {code} Still working on devstudio discovery. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 22:36:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 22:36:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-504: ----------------------------- Attachment: ea-in-non-ea.png Paul: can you purge the extraneous plugins from your 4.3.0.Alpha2 development folder? Or do you need me to do that? Surely you only have 1 or 2 plugins linked from the directory.xml files, so there's no need for a dozen nearly-identical copies of the same plugin in what should be a folder containing a SINGLE release. In this folder we see... * an extraneous directory.xml file not linked from anywhere, which refs an old version of your plugin: B425 (from Sept 17) * several old copies of the earlyaccess plugin (from B419 - B430) - yet there's a different EA folder with only 3 builds: B436 - B438: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins/ * several old copies of the non-ea plugin from B419 - B438 Then there's the problems in your EA site: * it doesn't contain both your plugins, only the EA one... so pointing a user at that site's directory.xml will only resolve the EA content, not the combination of EA and regular content. Seeing both at the same time paints a more realistic picture of what an end-user will see when the whole thing's live. And finally, I have to ask... why do you have two copies of the directory.xml files? * http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml are indentical so why produce both? * http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml are NOT identical, and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml lists the same JBT plugin TWICE, rather than listing the core and EA plugins (there ought to be 4 different plugins listed). Here's what a valid site looks like: http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml or https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/devstudio-directory.xml Hope that helps! !ea-in-non-ea.png! > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 22:37:03 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 22:37:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115714#comment-13115714 ] Nick Boldt edited comment on JBTIS-504 at 10/6/15 10:36 PM: ------------------------------------------------------------ Paul: can you purge the extraneous plugins from your 4.3.0.Alpha2 development folder? Or do you need me to do that? Surely you only have 1 or 2 plugins linked from the directory.xml files, so there's no need for a dozen nearly-identical copies of the same plugin in what should be a folder containing a SINGLE release. In this folder we see... [^ea-in-non-ea.png] * an extraneous directory.xml file not linked from anywhere, which refs an old version of your plugin: B425 (from Sept 17) * several old copies of the earlyaccess plugin (from B419 - B430) - yet there's a different EA folder with only 3 builds: B436 - B438: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins/ * several old copies of the non-ea plugin from B419 - B438 Then there's the problems in your EA site: * it doesn't contain both your plugins, only the EA one... so pointing a user at that site's directory.xml will only resolve the EA content, not the combination of EA and regular content. Seeing both at the same time paints a more realistic picture of what an end-user will see when the whole thing's live. And finally, I have to ask... why do you have two copies of the directory.xml files? * http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml are indentical so why produce both? * http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml are NOT identical, and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml lists the same JBT plugin TWICE, rather than listing the core and EA plugins (there ought to be 4 different plugins listed). Here's what a valid site looks like: http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml or https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/devstudio-directory.xml Hope that helps! was (Author: nickboldt): Paul: can you purge the extraneous plugins from your 4.3.0.Alpha2 development folder? Or do you need me to do that? Surely you only have 1 or 2 plugins linked from the directory.xml files, so there's no need for a dozen nearly-identical copies of the same plugin in what should be a folder containing a SINGLE release. In this folder we see... * an extraneous directory.xml file not linked from anywhere, which refs an old version of your plugin: B425 (from Sept 17) * several old copies of the earlyaccess plugin (from B419 - B430) - yet there's a different EA folder with only 3 builds: B436 - B438: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins/ * several old copies of the non-ea plugin from B419 - B438 Then there's the problems in your EA site: * it doesn't contain both your plugins, only the EA one... so pointing a user at that site's directory.xml will only resolve the EA content, not the combination of EA and regular content. Seeing both at the same time paints a more realistic picture of what an end-user will see when the whole thing's live. And finally, I have to ask... why do you have two copies of the directory.xml files? * http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml are indentical so why produce both? * http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-integration-stack-directory.xml and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml are NOT identical, and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml lists the same JBT plugin TWICE, rather than listing the core and EA plugins (there ought to be 4 different plugins listed). Here's what a valid site looks like: http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml or https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/devstudio-directory.xml Hope that helps! !ea-in-non-ea.png! > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 22:38:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 6 Oct 2015 22:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20708) tools.jboss.org/features: Add Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115716#comment-13115716 ] Nick Boldt commented on JBIDE-20708: ------------------------------------ Doesn't bother me as long as it gets done. :D > tools.jboss.org/features: Add Docker > ------------------------------------ > > Key: JBIDE-20708 > URL: https://issues.jboss.org/browse/JBIDE-20708 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, website > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > We should add Docker to tools.jboss.org/features -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 02:14:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Wed, 7 Oct 2015 02:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115731#comment-13115731 ] Misha Ali commented on JBDS-3516: --------------------------------- [~mickael_istria], you can add your details here, and I can add them to the doc once we settle on a final version, if that suits you. Our docs are not in git currently. > Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] > ------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3516 > URL: https://issues.jboss.org/browse/JBDS-3516 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, documentation, updatesite > Affects Versions: 9.0.0.CR1 > Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100 > jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0.0.CR1-updatesite-central.zip > Reporter: Jan Richter > Assignee: Mickael Istria > Fix For: 9.0.1.GA > > > This is what comes up when I try to install everything from the central zip: > {noformat} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 02:31:01 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 7 Oct 2015 02:31:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115735#comment-13115735 ] Mickael Istria commented on JBDS-3516: -------------------------------------- The part about Offline in the linked documentation seems to only cover the main JBDS installation, not the Central one. When installing Cental content offline, from Central zip, user has to also download the main JBDS zip, that contains some requirements from Central. Once user has both zips, from the installation wizard, click "Available Software Sites", then "Add" and choose "Archive" to specify the location of the the JBDS zip. Then user can go back to install wizard and select the Central zip as source and install content from it. > Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] > ------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3516 > URL: https://issues.jboss.org/browse/JBDS-3516 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, documentation, updatesite > Affects Versions: 9.0.0.CR1 > Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100 > jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0.0.CR1-updatesite-central.zip > Reporter: Jan Richter > Assignee: Mickael Istria > Fix For: 9.0.1.GA > > > This is what comes up when I try to install everything from the central zip: > {noformat} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:15:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: Konstantin Marmalyukov created JBIDE-20919: ---------------------------------------------- Summary: Target Platform: add jetty 9.3.2 bundles Key: JBIDE-20919 URL: https://issues.jboss.org/browse/JBIDE-20919 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Affects Versions: 4.4.0.Alpha1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.4.0.Alpha1 Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:17:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20920) Migrate livereload to jetty v 9.3.2 In-Reply-To: References: Message-ID: Konstantin Marmalyukov created JBIDE-20920: ---------------------------------------------- Summary: Migrate livereload to jetty v 9.3.2 Key: JBIDE-20920 URL: https://issues.jboss.org/browse/JBIDE-20920 Project: Tools (JBoss Tools) Issue Type: Task Components: browsersim, cordovasim Affects Versions: 4.4.0.Alpha1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.4.0.Alpha1 In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:17:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20920) Migrate livereload to jetty v 9.3.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20920: ------------------------------------------- Component/s: livereload (was: browsersim) (was: cordovasim) > Migrate livereload to jetty v 9.3.2 > ----------------------------------- > > Key: JBIDE-20920 > URL: https://issues.jboss.org/browse/JBIDE-20920 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:28:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov reassigned JBIDE-20919: ---------------------------------------------- Assignee: Mickael Istria (was: Konstantin Marmalyukov) > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:29:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115748#comment-13115748 ] Konstantin Marmalyukov commented on JBIDE-20919: ------------------------------------------------ Mickael, I need a first step - uploading jetty 9.2.3 bundles to download.jboss.org > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:30:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20919: ------------------------------------------- Issue Type: Feature Request (was: Task) > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:30:01 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20919: ------------------------------------------- Component/s: browsersim cordovasim livereload > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:34:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Wed, 7 Oct 2015 03:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115752#comment-13115752 ] Martin Malina commented on JBDS-3282: ------------------------------------- Thanks, [~akazakov], but keep in mind that the OpenShift 3 screencast still belongs to Fred ;) > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.1.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:38:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20919: ------------------------------------------- Description: *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works *Project page/sources:* http://www.eclipse.org/jetty/ *Version:* 9.2.3 *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ *JBoss mirror:* N/A *Include Sources:* No *Affected JBoss Tools components:* browsersim, cordovasim, livereload *Include in JBDS:* Yes *Type of dependency:*distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} was:Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* N/A > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:*distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:38:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 03:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20919: ------------------------------------------- Description: *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works *Project page/sources:* http://www.eclipse.org/jetty/ *Version:* 9.2.3 *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ *JBoss mirror:* N/A *Include Sources:* No *Affected JBoss Tools components:* browsersim, cordovasim, livereload *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} was: *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works *Project page/sources:* http://www.eclipse.org/jetty/ *Version:* 9.2.3 *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ *JBoss mirror:* N/A *Include Sources:* No *Affected JBoss Tools components:* browsersim, cordovasim, livereload *Include in JBDS:* Yes *Type of dependency:*distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* N/A > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 03:46:00 2015 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 7 Oct 2015 03:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Cannot update Arquillian feature 1.2.0.CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115757#comment-13115757 ] Marek Novotny commented on JBDS-3525: ------------------------------------- and it is here again with the 1.2.0.CR1 to 1.2.0.Final update, just fyi > Cannot update Arquillian feature 1.2.0.CR1 > ------------------------------------------ > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 04:09:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 04:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20919: ------------------------------------------- Description: *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works *Project page/sources:* http://www.eclipse.org/jetty/ *Version:* 9.2.3 *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ *JBoss mirror:* N/A *Include Sources:* No *Affected JBoss Tools components:* browsersim, cordovasim, livereload *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* See attached PR was: *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works *Project page/sources:* http://www.eclipse.org/jetty/ *Version:* 9.2.3 *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ *JBoss mirror:* N/A *Include Sources:* No *Affected JBoss Tools components:* browsersim, cordovasim, livereload *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* N/A > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 04:33:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 7 Oct 2015 04:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20919: ----------------------------------- Description: *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works *Project page/sources:* http://www.eclipse.org/jetty/ *Version:* 9.2.3 *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ *Include Sources:* No *Affected JBoss Tools components:* browsersim, cordovasim, livereload *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* See attached PR was: *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works *Project page/sources:* http://www.eclipse.org/jetty/ *Version:* 9.2.3 *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ *JBoss mirror:* N/A *Include Sources:* No *Affected JBoss Tools components:* browsersim, cordovasim, livereload *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* See attached PR > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 04:33:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 7 Oct 2015 04:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115784#comment-13115784 ] Mickael Istria commented on JBIDE-20919: ---------------------------------------- I created the mirror at http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 04:55:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 04:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115797#comment-13115797 ] Konstantin Marmalyukov commented on JBIDE-20919: ------------------------------------------------ So next step is applying PR and kicking TP build? > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 05:00:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 7 Oct 2015 05:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115802#comment-13115802 ] Mickael Istria commented on JBIDE-20919: ---------------------------------------- Since this change impacts several components, it seems necessary to notify about the proposal on the jbosstools-dev list to get all interested parties aware of this upcoming change, so they can try it locally. If you're interested, you can send the suggested mail: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#send-mail-for-feedback > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 05:12:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 05:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115812#comment-13115812 ] Konstantin Marmalyukov commented on JBIDE-20919: ------------------------------------------------ I'm not sure we need to send an email - the only persons who use jettys are me and Xavier. I talk with him this morning - he is fine with this update. I have already run all components with new jettys and fix all API updates. Now I need new TP to build components locally and create a PRs > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 05:16:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 7 Oct 2015 05:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115814#comment-13115814 ] Max Rydahl Andersen commented on JBIDE-20919: --------------------------------------------- Please always send an email when we do a major update to the target TP. Everyone has the possibility to be affected by this - not just you and Xavier. > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 05:17:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 7 Oct 2015 05:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115815#comment-13115815 ] Max Rydahl Andersen commented on JBIDE-20919: --------------------------------------------- btw. I know this update is a minor one in version numbers, but last time we did this for Jetty it had major impacts. > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 05:21:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 05:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115816#comment-13115816 ] Konstantin Marmalyukov commented on JBIDE-20919: ------------------------------------------------ {quote}btw. I know this update is a minor one in version numbers, but last time we did this for Jetty it had major impacts.{quote} I already test livereload and partly sims with my dev environmet(partly because my office windows machine doesn't work as should, have no idea why) - API changes are not very big, everything starts as it should. Now I would like to use new builded TP for testing into dev environment on another OS, where I don't have any problems :) {quote}Please always send an email when we do a major update to the target TP{quote} [~mickael_istria] I will send an announcing email now. > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 05:22:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 05:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115816#comment-13115816 ] Konstantin Marmalyukov edited comment on JBIDE-20919 at 10/7/15 5:21 AM: ------------------------------------------------------------------------- {quote}btw. I know this update is a minor one in version numbers, but last time we did this for Jetty it had major impacts.{quote} I already test livereload and partly sims with my dev environmet(partly because my office windows machine doesn't work as should, have no idea why) - API changes are not very big, everything starts as it should. Now I would like to use new builded TP for testing into dev environment on another OS, where I don't have any problems :) I remember our struggling with CR1 respin-a, so I will do everything carefully. {quote}Please always send an email when we do a major update to the target TP{quote} [~mickael_istria] I will send an announcing email now. was (Author: kmarmaliykov): {quote}btw. I know this update is a minor one in version numbers, but last time we did this for Jetty it had major impacts.{quote} I already test livereload and partly sims with my dev environmet(partly because my office windows machine doesn't work as should, have no idea why) - API changes are not very big, everything starts as it should. Now I would like to use new builded TP for testing into dev environment on another OS, where I don't have any problems :) {quote}Please always send an email when we do a major update to the target TP{quote} [~mickael_istria] I will send an announcing email now. > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 05:37:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Wed, 7 Oct 2015 05:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20921) Create tests for HibernateMappingExporterExtension classes In-Reply-To: References: Message-ID: Koen Aers created JBIDE-20921: --------------------------------- Summary: Create tests for HibernateMappingExporterExtension classes Key: JBIDE-20921 URL: https://issues.jboss.org/browse/JBIDE-20921 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 07:00:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 7 Oct 2015 07:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-500) Update BPMN2 Modeler for SwitchYard fix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-500. ----------------------------------- Verified with JBDS 9.0.0.CR2 + JBDS-IS 9.0.0.Alpha2 > Update BPMN2 Modeler for SwitchYard fix > --------------------------------------- > > Key: JBTIS-500 > URL: https://issues.jboss.org/browse/JBTIS-500 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: BPMN2 > Affects Versions: 9.0.0.Alpha1, 4.3.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.0.Alpha2, 4.3.0.Alpha2 > > > From [~apodhrad] > The update site https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.Alpha2/earlyaccess contains BPMN2 modeler older than at http://download.eclipse.org/bpmn2-modeler/updates/mars/1.2.1/ (the BPMN2 from 9.0.0.Alpha2 doesn't work correctly with SwitchYard but the one from eclipse works fine). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 08:43:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 7 Oct 2015 08:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115932#comment-13115932 ] Fred Bricon commented on JBDS-3282: ----------------------------------- I'm currently stuck by missing the proper material to perform some recording (working local/staging OS3 instance). [~mmalina] I can transfer ownership of that task back to you if you insist. I'd be delighted :-) > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.1.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 08:48:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Wed, 7 Oct 2015 08:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115936#comment-13115936 ] Martin Malina commented on JBDS-3282: ------------------------------------- [~fbricon], thanks, but no, thanks :) > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.1.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 08:59:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Wed, 7 Oct 2015 08:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20903: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Need to split org.jboss.tools.jst.js to *.node and *.bower > ---------------------------------------------------------- > > Key: JBIDE-20903 > URL: https://issues.jboss.org/browse/JBIDE-20903 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: > * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) > * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) > it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:40:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20918: ------------------------------------------- Summary: Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP (was: Migrate browsersim and cordovasim to jetty v 9.3.2) > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:40:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20920) Livereload is broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20920: ------------------------------------------- Summary: Livereload is broken since jetty v 9.3.2 was added to TP (was: Migrate livereload to jetty v 9.3.2) > Livereload is broken since jetty v 9.3.2 was added to TP > -------------------------------------------------------- > > Key: JBIDE-20920 > URL: https://issues.jboss.org/browse/JBIDE-20920 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:44:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20920) Livereload is broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20920: ------------------------------------------- Description: In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. The reason why Livereload cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 was:In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > Livereload is broken since jetty v 9.3.2 was added to TP > -------------------------------------------------------- > > Key: JBIDE-20920 > URL: https://issues.jboss.org/browse/JBIDE-20920 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Livereload cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:44:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20918: ------------------------------------------- Issue Type: Bug (was: Task) > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:44:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20920) Livereload is broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20920: ------------------------------------------- Issue Type: Bug (was: Task) > Livereload is broken since jetty v 9.3.2 was added to TP > -------------------------------------------------------- > > Key: JBIDE-20920 > URL: https://issues.jboss.org/browse/JBIDE-20920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Livereload cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:44:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20918: ------------------------------------------- Description: In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 was:In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:48:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20918: ------------------------------------------- Description: In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 See JBIDE-20670 for more details was: In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:48:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 7 Oct 2015 10:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20920) Livereload is broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov updated JBIDE-20920: ------------------------------------------- Description: In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. The reason why Livereload cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 See JBIDE-20670 for more details was: In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. The reason why Livereload cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > Livereload is broken since jetty v 9.3.2 was added to TP > -------------------------------------------------------- > > Key: JBIDE-20920 > URL: https://issues.jboss.org/browse/JBIDE-20920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Livereload cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 11:04:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Wed, 7 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116055#comment-13116055 ] Ilya Buziuk commented on JBIDE-20903: ------------------------------------- PR was sent > Need to split org.jboss.tools.jst.js to *.node and *.bower > ---------------------------------------------------------- > > Key: JBIDE-20903 > URL: https://issues.jboss.org/browse/JBIDE-20903 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: > * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) > * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) > it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 11:10:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 7 Oct 2015 11:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116061#comment-13116061 ] Alexey Kazakov commented on JBDS-3282: -------------------------------------- Sorry, it was a bulk change for all screencasts tasks with the same comment ;-) > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.0.1.GA > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 12:19:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 7 Oct 2015 12:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20922) [website] need a default landing page in whatsnew folder In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20922: ---------------------------------- Summary: [website] need a default landing page in whatsnew folder Key: JBIDE-20922 URL: https://issues.jboss.org/browse/JBIDE-20922 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.3.0.Final Reporter: Nick Boldt This page is blank / forbidden: http://tools.jboss.org/documentation/whatsnew/jbosstools/ Yet this page is fine. http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html Could we have a default index.html that redirects to the latest whatsnew version, so it's easier to link to the latest w/o knowing the version? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 12:21:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 7 Oct 2015 12:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20922) [website] need a default landing page in whatsnew folder In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116107#comment-13116107 ] Alexey Kazakov commented on JBIDE-20922: ---------------------------------------- +1! > [website] need a default landing page in whatsnew folder > -------------------------------------------------------- > > Key: JBIDE-20922 > URL: https://issues.jboss.org/browse/JBIDE-20922 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > > This page is blank / forbidden: > http://tools.jboss.org/documentation/whatsnew/jbosstools/ > Yet this page is fine. > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html > Could we have a default index.html that redirects to the latest whatsnew version, so it's easier to link to the latest w/o knowing the version? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 12:22:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 7 Oct 2015 12:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20922) [website] need a default landing page in whatsnew folder In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20922: -------------------------------------- Assignee: Xavier Coulon > [website] need a default landing page in whatsnew folder > -------------------------------------------------------- > > Key: JBIDE-20922 > URL: https://issues.jboss.org/browse/JBIDE-20922 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Xavier Coulon > > This page is blank / forbidden: > http://tools.jboss.org/documentation/whatsnew/jbosstools/ > Yet this page is fine. > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html > Could we have a default index.html that redirects to the latest whatsnew version, so it's easier to link to the latest w/o knowing the version? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 15:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 7 Oct 2015 15:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20903: ----------------------------------- Issue Type: Task (was: Enhancement) > Need to split org.jboss.tools.jst.js to *.node and *.bower > ---------------------------------------------------------- > > Key: JBIDE-20903 > URL: https://issues.jboss.org/browse/JBIDE-20903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: > * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) > * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) > it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 18:46:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 7 Oct 2015 18:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116203#comment-13116203 ] Paul Leacu commented on JBTIS-504: ---------------------------------- Hey [~nickboldt] I've cleaned everything up and it all seems to work okay. Please review: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/plugins http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/composite* http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/plugins https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/composite* https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/plugins https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/composite* https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/plugins To test JBTIS: {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2 \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess {code} To test JBDSIS: {code} ./jbdevstudio -vmargs \ -Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml \ -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2 \ -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess {code} > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 22:44:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 7 Oct 2015 22:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Cannot update Arquillian feature 1.2.0.CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116229#comment-13116229 ] Nick Boldt commented on JBDS-3525: ---------------------------------- Have you tried enabling Early Access and then doing an install via Central, rather than an update? Arquillian isn't strictly part of JBDS or JBDS Central -- it's only part of the Early Access site, which is only exposed through Central's Software/Update tab. Weird that it notifies there's an update available (so it must be hitting the EA site) but then can't see the site to do the install. This is definitely something we should look at for 9.1 / 10.0 > Cannot update Arquillian feature 1.2.0.CR1 > ------------------------------------------ > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 00:13:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 8 Oct 2015 00:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20838: ----------------------------------- Assignee: Fred Bricon > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Minor > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 00:14:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 8 Oct 2015 00:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20838: -------------------------------- Fix Version/s: 4.4.x > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.x > > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 00:19:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 8 Oct 2015 00:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116235#comment-13116235 ] Fred Bricon commented on JBIDE-20838: ------------------------------------- [~ldimaggio]: didn't you get a message dialog asking you to restart Eclipse after you installed the missing packages? Not sure we can (easily) detect the required features have been downloaded but not installed. Might need to make the Central page listen to the Software installation process. [~mickael_istria], [~snjeza] any idea? > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.x > > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 01:16:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 8 Oct 2015 01:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116248#comment-13116248 ] Mickael Istria commented on JBIDE-20838: ---------------------------------------- {quote}Not sure we can (easily) detect the required features have been downloaded but not installed.{quote} IIRC, the restart isn't required by p2. It's there because many plugins consuming extensions load them only once per instance and cannot see contributions added on the fly, so many parts of the IDE won't notice new contributions brought by newly installed software, leading to a confusing state for users. Maybe the dialog should tell more at that point. "This example wizard requires additional feature to be installed. Clicking OK to install the required feature and then restart your IDE. After restart, you'll be able to use this example wizard." > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.x > > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 02:26:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 02:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20689) Skip tests that cannot run on current platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116259#comment-13116259 ] Denis Golovin commented on JBIDE-20689: --------------------------------------- That is correct, except it works only for JUnit 4 annotated tests, if test extends TestCase then assume doesn't skip the test it marks it as a error/failure. Attached fix includes both: 1. assumeTrue to verify supported platform and GTK3 2. migration to annotated JUnit4 tests > Skip tests that cannot run on current platform > ---------------------------------------------- > > Key: JBIDE-20689 > URL: https://issues.jboss.org/browse/JBIDE-20689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.4.x > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.x > > > VPE related run without errors only only on certain platforms. They should be skipped during tests execution and appear as skipped in report. As an example javaee tests now fail to pass under Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 02:36:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 02:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20689) Skip tests that cannot run on current platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20689: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/456, https://github.com/jbosstools/jbosstools-jst/pull/533, https://github.com/jbosstools/jbosstools-vpe/pull/329, https://github.com/jbosstools/jbosstools-javaee/pull/381 (was: https://github.com/jbosstools/jbosstools-base/pull/456) > Skip tests that cannot run on current platform > ---------------------------------------------- > > Key: JBIDE-20689 > URL: https://issues.jboss.org/browse/JBIDE-20689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.4.x > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.x > > > VPE related run without errors only only on certain platforms. They should be skipped during tests execution and appear as skipped in report. As an example javaee tests now fail to pass under Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 02:37:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 02:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20689) Skip tests that cannot run on current platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20689: ---------------------------------- Fix Version/s: (was: 4.4.x) > Skip tests that cannot run on current platform > ---------------------------------------------- > > Key: JBIDE-20689 > URL: https://issues.jboss.org/browse/JBIDE-20689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.4.x > Reporter: Denis Golovin > Assignee: Denis Golovin > > VPE related run without errors only only on certain platforms. They should be skipped during tests execution and appear as skipped in report. As an example javaee tests now fail to pass under Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 02:38:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 02:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20689) Skip tests that cannot run on current platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20689: ---------------------------------- Affects Version/s: 4.4.0.Alpha1 (was: 4.4.x) > Skip tests that cannot run on current platform > ---------------------------------------------- > > Key: JBIDE-20689 > URL: https://issues.jboss.org/browse/JBIDE-20689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > VPE related run without errors only only on certain platforms. They should be skipped during tests execution and appear as skipped in report. As an example javaee tests now fail to pass under Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 02:38:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 02:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20689) Skip tests that cannot run on current platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20689: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 > Skip tests that cannot run on current platform > ---------------------------------------------- > > Key: JBIDE-20689 > URL: https://issues.jboss.org/browse/JBIDE-20689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > VPE related run without errors only only on certain platforms. They should be skipped during tests execution and appear as skipped in report. As an example javaee tests now fail to pass under Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 03:29:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 8 Oct 2015 03:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116278#comment-13116278 ] Max Rydahl Andersen commented on JBIDE-20919: --------------------------------------------- so even if you say the api changes are not very big this I assume means changes in master is no longer trivial to merge to do fixes on the mars branch. > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 03:40:00 2015 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Thu, 8 Oct 2015 03:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Cannot update Arquillian feature 1.2.0.CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116283#comment-13116283 ] Marek Novotny commented on JBDS-3525: ------------------------------------- Hey [~nickboldt] see Environment field, where I wrote I have got enabled Early Access. Currently on Version: 9.0.0.GA Build id: GA-v20151002-2235-B124 Build date: 20151002-2235 So every other update works, just that Arquillian support update not. I don't mind, but everytime I launch JBDS it bugs me with it and what works manually is uninstall it and install again from zero to have the latest version. And yes It seems to me totally weird if it notifies me and then a few seconds after it can't find it. > Cannot update Arquillian feature 1.2.0.CR1 > ------------------------------------------ > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 03:55:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Thu, 8 Oct 2015 03:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7) In-Reply-To: References: Message-ID: Radim Hopp created JBIDE-20923: ---------------------------------- Summary: Wrong archetype is picked for unreleased EAP (7) Key: JBIDE-20923 URL: https://issues.jboss.org/browse/JBIDE-20923 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.3.0.Final Reporter: Radim Hopp When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype). Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 05:19:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Thu, 8 Oct 2015 05:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116322#comment-13116322 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- > Took the SS and sent an email to misha to see if we can add it to the guide > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 05:47:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Thu, 8 Oct 2015 05:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116328#comment-13116328 ] Konstantin Marmalyukov commented on JBIDE-20919: ------------------------------------------------ {quote}so even if you say the api changes are not very big this I assume means changes in master is no longer trivial to merge to do fixes on the mars branch. {quote} I think we will not need to merge any things in master branch - I hope next Eclipse Mars releases will stay with Jetty v9.2.13. Even if they will change jetty version - yes, it will be no problem for us to merge with 4.3 branch > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 08:32:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 8 Oct 2015 08:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20829) Support of krb5-principal keys in openshift-java-client (eclipse) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116388#comment-13116388 ] Andre Dietisheim commented on JBIDE-20829: ------------------------------------------ retargeting this to openshift 3 > Support of krb5-principal keys in openshift-java-client (eclipse) > ------------------------------------------------------------------ > > Key: JBIDE-20829 > URL: https://issues.jboss.org/browse/JBIDE-20829 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Christos Triantafyllidis > Assignee: Andre Dietisheim > Fix For: 4.3.x > > > The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. > This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. > https://github.com/openshift/openshift-java-client/blob/master/src/main/java/com/openshift/client/SSHKeyType.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 08:32:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 8 Oct 2015 08:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20829) Support of krb5-principal keys in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20829: ------------------------------------- Summary: Support of krb5-principal keys in openshift (was: Support of krb5-principal keys in openshift-java-client (eclipse)) > Support of krb5-principal keys in openshift > -------------------------------------------- > > Key: JBIDE-20829 > URL: https://issues.jboss.org/browse/JBIDE-20829 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Christos Triantafyllidis > Assignee: Andre Dietisheim > Fix For: 4.3.x > > > The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. > This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. > https://github.com/openshift/openshift-java-client/blob/master/src/main/java/com/openshift/client/SSHKeyType.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 08:44:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 8 Oct 2015 08:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Cannot update Arquillian feature 1.2.0.CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116397#comment-13116397 ] Max Rydahl Andersen commented on JBDS-3525: ------------------------------------------- Marek/Nick, something is obviously wrong if users are getting https://devstudio.redhat.com/9.0/staging/updates/core/9.0.0.Beta2b into their list of updatesites - those aren't part of what we release for /development nor /stable right ? Marek -can you post the exact errors you see because the end-user visible error might look the same but behind the scenes it is something else. > Cannot update Arquillian feature 1.2.0.CR1 > ------------------------------------------ > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:29:01 2015 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Thu, 8 Oct 2015 09:29:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Cannot update Arquillian feature 1.2.0.CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116428#comment-13116428 ] Marek Novotny commented on JBDS-3525: ------------------------------------- [~maxandersen] it certainly is not referencing https://devstudio.redhat.com/9.0/staging/updates/core/9.0.0.Beta2b as that was for the Update to 1.2.0.CR1 and I removed that update site manually after I created the comment -> https://issues.jboss.org/browse/JBDS-3525?focusedCommentId=13110271&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110271. I just was notified about 1.2.0.Final update in JBDS so I got a go and then it wasn't found, I don't recall the error message, but I am pasting what was in worskpace log {noformat} !SESSION 2015-10-08 09:35:04.775 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_60 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product Command-line arguments: -os linux -ws gtk -arch x86_64 -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product !ENTRY org.eclipse.equinox.p2.engine 4 4 2015-10-08 09:40:01.897 !MESSAGE An error occurred while collecting items to be installed !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2015-10-08 09:40:01.897 !MESSAGE session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2015-10-08 09:40:01.897 !MESSAGE No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.Final-v20150925-0253-B27 !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2015-10-08 09:40:01.897 !MESSAGE No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.Final-v20150925-0253-B27 !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2015-10-08 09:40:01.897 !MESSAGE No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.Final-v20150925-0253-B27 !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2015-10-08 09:40:01.897 !MESSAGE No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.Final-v20150925-0253-B27 !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) at sun.security.ssl.InputRecord.read(InputRecord.java:532) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 !MESSAGE Unexpected error !STACK 0 java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) ... 8 more Caused by: org.eclipse.core.runtime.OperationCanceledException at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) ... 13 more {noformat} > Cannot update Arquillian feature 1.2.0.CR1 > ------------------------------------------ > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:32:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 8 Oct 2015 09:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: Andrej Podhradsky created JBDS-3537: --------------------------------------- Summary: Connection problems with https://devstudio.jboss.com/ Key: JBDS-3537 URL: https://issues.jboss.org/browse/JBDS-3537 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: website Reporter: Andrej Podhradsky Priority: Blocker Recently, I have connection problems with https://devstudio.jboss.com/ For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:33:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Thu, 8 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116435#comment-13116435 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- > Replaced SS (install jbds byoe when onilne, fig. 2) with one for GA > Made an entry in Rev History Hi [~mhusnain], can you please brew this? Thanks - supriya Content Spec ID: 23020 DocBuilder Link: http://docbuilder.usersys.redhat.com/23020/ > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:38:01 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Thu, 8 Oct 2015 09:38:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20903: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/531, https://github.com/jbosstools/jbosstools-jst/pull/534 (was: https://github.com/jbosstools/jbosstools-jst/pull/531) > Need to split org.jboss.tools.jst.js to *.node and *.bower > ---------------------------------------------------------- > > Key: JBIDE-20903 > URL: https://issues.jboss.org/browse/JBIDE-20903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: > * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) > * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) > it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:38:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:38:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Cannot update Arquillian feature 1.2.0.CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116440#comment-13116440 ] Nick Boldt commented on JBDS-3525: ---------------------------------- Related to JBIDE-18876 but not a dupe. > Cannot update Arquillian feature 1.2.0.CR1 > ------------------------------------------ > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:41:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: Nick Boldt created JBDS-3538: -------------------------------- Summary: read timeouts accessing JBDS discovery bits (possible Akamai problem?) Key: JBDS-3538 URL: https://issues.jboss.org/browse/JBDS-3538 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Nick Boldt As reported in JBDS-3525: {code} !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) at sun.security.ssl.InputRecord.read(InputRecord.java:532) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 !MESSAGE Unexpected error java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) ... 8 more Caused by: org.eclipse.core.runtime.OperationCanceledException at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:42:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3538: ----------------------------- Fix Version/s: 9.0.x > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Fix For: 9.0.x > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:42:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3525: ----------------------------- Summary: Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) (was: Cannot update Arquillian feature 1.2.0.CR1) > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:42:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3538: ----------------------------- Component/s: central discovery updatesite > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Fix For: 9.0.x > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:42:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3538: ----------------------------- Affects Version/s: 9.0.0.GA > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Fix For: 9.0.x > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:43:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 8 Oct 2015 09:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3538: ----------------------------- > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Fix For: 9.0.x > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:43:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3538: ----------------------------- Status: New (was: New) Target Release: 9.1.0.GA > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Fix For: 9.0.x > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:44:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 09:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3538: ----------------------------- Description: As reported in JBDS-3525: {code} !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) at sun.security.ssl.InputRecord.read(InputRecord.java:532) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 !MESSAGE Unexpected error java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) ... 8 more Caused by: org.eclipse.core.runtime.OperationCanceledException at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) ... 13 more{code} was: As reported in JBDS-3525: {code} !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 !MESSAGE Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: Read timed out java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) at sun.security.ssl.InputRecord.read(InputRecord.java:532) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 !MESSAGE Unexpected error java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) ... 8 more Caused by: org.eclipse.core.runtime.OperationCanceledException at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) ... 13 more{code} > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Fix For: 9.0.x > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:56:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 09:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116449#comment-13116449 ] Alexey Kazakov commented on JBIDE-20919: ---------------------------------------- We need to keep an eye on Jetty in both Mars.2 and Neon streams. Don't wait for their release hopping they will do everything properly. We should track Jetty version changes during the development process. > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 09:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 09:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3525: --------------------------------- Fix Version/s: 9.0.1.GA 10.0.0.Alpha1 > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:17:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Thu, 8 Oct 2015 10:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20924) Write a blog about the changes in the Eclipse Hibernate tooling In-Reply-To: References: Message-ID: Koen Aers created JBIDE-20924: --------------------------------- Summary: Write a blog about the changes in the Eclipse Hibernate tooling Key: JBIDE-20924 URL: https://issues.jboss.org/browse/JBIDE-20924 Project: Tools (JBoss Tools) Issue Type: Task Components: website Reporter: Koen Aers Assignee: Koen Aers -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:21:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Thu, 8 Oct 2015 10:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116480#comment-13116480 ] Len DiMaggio commented on JBIDE-20838: -------------------------------------- +1 on simply changing the dialog text to inform the user that he/she will be able to install the example after eclipse restarts. Thx! > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.x > > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:29:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 8 Oct 2015 10:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3537: ----------------------------- > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Priority: Blocker > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:29:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 10:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3537: ----------------------------- Status: New (was: New) Target Release: 9.1.0.GA > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Priority: Blocker > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:48:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Thu, 8 Oct 2015 10:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116508#comment-13116508 ] Konstantin Marmalyukov commented on JBIDE-20919: ------------------------------------------------ I thought we are. But during last jetty migration I brake a test which detects this problem - sorry. But this detection happens only after TP is updated with new Eclipse release- so here comes question to [~nickboldt] and [~mickael_istria]: How soon after Eclipse release we having the changes into TP? > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:52:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 8 Oct 2015 10:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116512#comment-13116512 ] Mickael Istria commented on JBIDE-20919: ---------------------------------------- {quote}How soon after Eclipse release we having the changes into TP?{quote} Depends on how much teammates are needing the change. If it's a critical thing we need to adopt ASAP, we can update TP on the same day as the milestone; if there is no breaking change, then it depends on our mood ;) > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/ > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 11:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 11:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3537: ------------------------------------ Assignee: Nick Boldt > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 11:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 11:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3537: --------------------------------- Fix Version/s: 9.0.1.GA 10.0.0.Alpha1 > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 11:39:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 11:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3538: --------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.x) > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 11:39:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 11:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3538: --------------------------------- Priority: Blocker (was: Major) > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 11:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 11:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3538: ------------------------------------ Assignee: Nick Boldt > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 11:47:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 11:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20924) Write a blog about the changes in the Eclipse Hibernate tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20924: ----------------------------------- Fix Version/s: 4.3.1.Final > Write a blog about the changes in the Eclipse Hibernate tooling > --------------------------------------------------------------- > > Key: JBIDE-20924 > URL: https://issues.jboss.org/browse/JBIDE-20924 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 15:57:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Thu, 8 Oct 2015 15:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116643#comment-13116643 ] Paul Leacu commented on JBTIS-504: ---------------------------------- [~nickboldt] - Added generic version-free URLs for the IS discovery sites: http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/earlyaccess https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess To test JBTIS: {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/earlyaccess {code} To test JBDSIS: {code} ./jbdevstudio -vmargs \ -Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml \ -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery \ -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess {code} > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 16:12:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 16:12:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116647#comment-13116647 ] Nick Boldt commented on JBIDE-18820: ------------------------------------ New document: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versioning-build-artifacts.adoc Commit: https://github.com/jbosstools/jbosstools-devdoc/commit/d8c09494ba4fa827b3e7645be004000f1a84e9af [~maxandersen] Please review & throw me a PR for changes you'd like to see in the doc. Or, if you love what's there, feel free to resolve/close this JIRA. Thanks! > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.1.Final > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 16:15:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 16:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20925) bump currentversion.properties to latest JBT versions In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20925: ---------------------------------- Summary: bump currentversion.properties to latest JBT versions Key: JBIDE-20925 URL: https://issues.jboss.org/browse/JBIDE-20925 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 Reporter: Nick Boldt Priority: Blocker Per https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versioning-build-artifacts.adoc it's time to update the values of default.version in foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 16:16:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 16:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20925) bump currentversion.properties to latest JBT versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20925: ------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 > bump currentversion.properties to latest JBT versions > ----------------------------------------------------- > > Key: JBIDE-20925 > URL: https://issues.jboss.org/browse/JBIDE-20925 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > Per https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versioning-build-artifacts.adoc it's time to update the values of default.version in foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 16:20:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 16:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20926) Visual Preview tests fail on windows In-Reply-To: References: Message-ID: Denis Golovin created JBIDE-20926: ------------------------------------- Summary: Visual Preview tests fail on windows Key: JBIDE-20926 URL: https://issues.jboss.org/browse/JBIDE-20926 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core Affects Versions: 4.4.0.Alpha1 Reporter: Denis Golovin Assignee: Konstantin Marmalyukov Fix For: 4.4.0.Alpha1 {code}externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.671 sec <<< ERROR! java.lang.Exception: Refresh does not happens at org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest.externalUrlReloadTest(PreviewReloadTest.java:72) externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.681 sec <<< FAILURE! java.lang.AssertionError: Refresh does not happens at org.junit.Assert.fail(Assert.java:88) at org.jboss.tools.vpe.preview.editor.test.editor.VpvTest.failOnException(VpvTest.java:68) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) 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:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 16:21:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 16:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20926) Visual Preview tests fail on windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20926: ---------------------------------- Environment: Windows IE11 x86_64 > Visual Preview tests fail on windows > ------------------------------------ > > Key: JBIDE-20926 > URL: https://issues.jboss.org/browse/JBIDE-20926 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha1 > Environment: Windows IE11 x86_64 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > {code}externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.671 sec <<< ERROR! > java.lang.Exception: Refresh does not happens > at org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest.externalUrlReloadTest(PreviewReloadTest.java:72) > externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.681 sec <<< FAILURE! > java.lang.AssertionError: Refresh does not happens > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.tools.vpe.preview.editor.test.editor.VpvTest.failOnException(VpvTest.java:68) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 16:24:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 16:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: Denis Golovin created JBIDE-20927: ------------------------------------- Summary: Validation framework errors in tests on jenkins Key: JBIDE-20927 URL: https://issues.jboss.org/browse/JBIDE-20927 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html-source-editing Affects Versions: 4.4.0.Alpha1 Reporter: Denis Golovin {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. !STACK 1 org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. !STACK 1 org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 18:07:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 18:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20925) bump currentversion.properties to latest JBT versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20925: -------------------------------------- Assignee: Nick Boldt Resolution: Done > bump currentversion.properties to latest JBT versions > ----------------------------------------------------- > > Key: JBIDE-20925 > URL: https://issues.jboss.org/browse/JBIDE-20925 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > Per https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versioning-build-artifacts.adoc it's time to update the values of default.version in foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 18:44:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 18:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20908) Upgrade FreeMarker to 2.3.23 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin reassigned JBIDE-20908: ------------------------------------- Assignee: Daniel Azarov (was: Denis Golovin) > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20908 > URL: https://issues.jboss.org/browse/JBIDE-20908 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Daniel Azarov > Fix For: 4.3.1.Final > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 18:52:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 8 Oct 2015 18:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1608) Feature set selection during installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-1608: -------------------------------- > Feature set selection during installation > ----------------------------------------- > > Key: JBDS-1608 > URL: https://issues.jboss.org/browse/JBDS-1608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Minor > > There are many wishes to make JBDS more modular so one way would be to allow feature selection during installation known from othere application where you can select what features/plugins should be installed during installation process and according to user selection final installation is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 18:52:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 18:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1608) Feature set selection during installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1608: -------------------------------- Fix Version/s: (was: LATER) > Feature set selection during installation > ----------------------------------------- > > Key: JBDS-1608 > URL: https://issues.jboss.org/browse/JBDS-1608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Minor > > There are many wishes to make JBDS more modular so one way would be to allow feature selection during installation known from othere application where you can select what features/plugins should be installed during installation process and according to user selection final installation is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 19:00:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 19:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1608) Feature set selection during installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin closed JBDS-1608. ------------------------------- Fix Version/s: JBDS-3395 Resolution: Duplicate Issue > Feature set selection during installation > ----------------------------------------- > > Key: JBDS-1608 > URL: https://issues.jboss.org/browse/JBDS-1608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Minor > Fix For: JBDS-3395 > > > There are many wishes to make JBDS more modular so one way would be to allow feature selection during installation known from othere application where you can select what features/plugins should be installed during installation process and according to user selection final installation is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 19:02:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 8 Oct 2015 19:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1608) Feature set selection during installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin closed JBDS-1608. ------------------------------- Resolution: Duplicate Issue > Feature set selection during installation > ----------------------------------------- > > Key: JBDS-1608 > URL: https://issues.jboss.org/browse/JBDS-1608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Minor > > There are many wishes to make JBDS more modular so one way would be to allow feature selection during installation known from othere application where you can select what features/plugins should be installed during installation process and according to user selection final installation is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 20:10:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 20:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20928) Improve operations that require Structured Source Editor model In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20928: -------------------------------------- Summary: Improve operations that require Structured Source Editor model Key: JBIDE-20928 URL: https://issues.jboss.org/browse/JBIDE-20928 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Reporter: Alexey Kazakov Assignee: Denis Golovin Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 20:13:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 20:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20928) Improve operations that require Structured Source Editor model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20928. ------------------------------------ Resolution: Done {quote} StructuredModelWrapper update to allow return result from command. Fix contains new Command2 class with T execute(IStructuredModel model) method to allow return an object from the command. That way tricks with passing return through final local array variable are not required anymore. {quote} > Improve operations that require Structured Source Editor model > -------------------------------------------------------------- > > Key: JBIDE-20928 > URL: https://issues.jboss.org/browse/JBIDE-20928 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 20:13:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 20:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20928) Improve operations that require Structured Source Editor model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20928. ---------------------------------- > Improve operations that require Structured Source Editor model > -------------------------------------------------------------- > > Key: JBIDE-20928 > URL: https://issues.jboss.org/browse/JBIDE-20928 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 20:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 20:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20927: -------------------------------------- Assignee: Viacheslav Kabanovich We should fix it and make sure it work fine in both master and 4.3.x. > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 20:26:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 20:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20927: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 20:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 8 Oct 2015 20:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20926) Visual Preview tests fail on windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116693#comment-13116693 ] Alexey Kazakov commented on JBIDE-20926: ---------------------------------------- Is it a pure test problem or it fails in runtime too? > Visual Preview tests fail on windows > ------------------------------------ > > Key: JBIDE-20926 > URL: https://issues.jboss.org/browse/JBIDE-20926 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha1 > Environment: Windows IE11 x86_64 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > {code}externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.671 sec <<< ERROR! > java.lang.Exception: Refresh does not happens > at org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest.externalUrlReloadTest(PreviewReloadTest.java:72) > externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.681 sec <<< FAILURE! > java.lang.AssertionError: Refresh does not happens > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.tools.vpe.preview.editor.test.editor.VpvTest.failOnException(VpvTest.java:68) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 22:47:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 22:47:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-504: ----------------------------- Attachment: JBDSIS-preview1.png JBDSIS-preview2-EA.png JBTIS-preview1.png JBTIS-preview2-EA.png Aesthetically, comparing these two: {quote} "JBoss Developer Studio 9.x - Integration Stack" - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/compositeArtifacts.xml "JBoss Tools Integration Stack 4.3 - Development Milestone" - http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/compositeArtifacts.xml {quote} I see divergent title conventions. This is non-blocking, but sloppy. * Why 9.x but 4.3 (not 4.3.x) ? * Why is only one of them a "Development Milestone" ? * Why change the ordering from "9.x - Integration Stack" to "Integration Stack 4.3" ? * And shouldn't that be "*Red Hat* JBoss Developer Studio", to adhere to correct branding rules? ---- Functionally speaking: https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml and https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/devstudio-directory.xml contain the same 3 plugins. Why build both when the contents are the same? Did you mean to include the JBDS EA plugin in there too? http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml contains only 3 of the 4 required plugins, as did 9.0.0.Alpha2/devstudio-directory.xml above. Why not include all 4? http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml contains all 4! Hooray! We have a fully-functional site for testing, which will show all the JBT, JBTEA , JBTIS, and JBTISEA content in a single Central view. [^JBTIS-preview1.png] & [^JBTIS-preview2-EA.png] Successfully installed everything. But for JBDS IS preview: [^JBDSIS-preview1.png] [^JBDSIS-preview2-EA.png] ... sadly there's no Arquillian available when Early Access is enabled, because the JBDS EA plugin is missing from the URL you provided as the testing site. :( So, this is only a problem w/ the test site, not the eventual JBDS site into which you'll add your plugins. But it will certainly confuse QE and break install-grinder tests. Can you produce a discovery site w/ all 4 JBDS plugins in it? > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 22:48:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 22:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116696#comment-13116696 ] Nick Boldt edited comment on JBTIS-504 at 10/8/15 10:47 PM: ------------------------------------------------------------ Aesthetically, comparing these two: {quote} "JBoss Developer Studio 9.x - Integration Stack" - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/compositeArtifacts.xml "JBoss Tools Integration Stack 4.3 - Development Milestone" - http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/compositeArtifacts.xml {quote} I see divergent title conventions. This is non-blocking, but sloppy. * Why 9.x but 4.3 (not 4.3.x) ? * Why is only one of them a "Development Milestone" ? * Why change the ordering from "9.x - Integration Stack" to "Integration Stack 4.3" ? * And shouldn't that be "*Red Hat* JBoss Developer Studio", to adhere to correct branding rules? ---- Functionally speaking: https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml and https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/devstudio-directory.xml contain the same 3 plugins. Why build both when the contents are the same? Did you mean to include the JBDS EA plugin in there too? http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml contains only 3 of the 4 required plugins, as did 9.0.0.Alpha2/devstudio-directory.xml above. Why not include all 4? http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml contains all 4! Hooray! We have a fully-functional site for testing, which will show all the JBT, JBTEA , JBTIS, and JBTISEA content in a single Central view. * [^JBTIS-preview1.png] & * [^JBTIS-preview2-EA.png] Successfully installed everything. But for JBDS IS preview: * [^JBDSIS-preview1.png] & * [^JBDSIS-preview2-EA.png] ... sadly there's no Arquillian available when Early Access is enabled, because the JBDS EA plugin is missing from the URL you provided as the testing site. :( So, this is only a problem w/ the test site, not the eventual JBDS site into which you'll add your plugins. But it will certainly confuse QE and break install-grinder tests. Can you produce a discovery site w/ all 4 JBDS plugins in it? was (Author: nickboldt): Aesthetically, comparing these two: {quote} "JBoss Developer Studio 9.x - Integration Stack" - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/compositeArtifacts.xml "JBoss Tools Integration Stack 4.3 - Development Milestone" - http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/compositeArtifacts.xml {quote} I see divergent title conventions. This is non-blocking, but sloppy. * Why 9.x but 4.3 (not 4.3.x) ? * Why is only one of them a "Development Milestone" ? * Why change the ordering from "9.x - Integration Stack" to "Integration Stack 4.3" ? * And shouldn't that be "*Red Hat* JBoss Developer Studio", to adhere to correct branding rules? ---- Functionally speaking: https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml and https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/devstudio-directory.xml contain the same 3 plugins. Why build both when the contents are the same? Did you mean to include the JBDS EA plugin in there too? http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml contains only 3 of the 4 required plugins, as did 9.0.0.Alpha2/devstudio-directory.xml above. Why not include all 4? http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/jbosstools-directory.xml contains all 4! Hooray! We have a fully-functional site for testing, which will show all the JBT, JBTEA , JBTIS, and JBTISEA content in a single Central view. [^JBTIS-preview1.png] & [^JBTIS-preview2-EA.png] Successfully installed everything. But for JBDS IS preview: [^JBDSIS-preview1.png] [^JBDSIS-preview2-EA.png] ... sadly there's no Arquillian available when Early Access is enabled, because the JBDS EA plugin is missing from the URL you provided as the testing site. :( So, this is only a problem w/ the test site, not the eventual JBDS site into which you'll add your plugins. But it will certainly confuse QE and break install-grinder tests. Can you produce a discovery site w/ all 4 JBDS plugins in it? > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 22:53:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 22:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-487) SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-487: ----------------------------- Attachment: IS-projects-using-old-license.png IS-projects-using-old-license_2.png Don't mean to piss in your cornflakes, but when I look at the latest JBT IS 4.3. Alpha2 / JBDS IS 9.0.0.Alpha2 bits I see this: * in JBT: !IS-projects-using-old-license.png! * in JBDS: !IS-projects-using-old-license_2.png! is this because you didn't publish your newer bits into the IS? Or is the problem in SwitchYard itself? What's the latest version available w/ the fixed features / license terms? > SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------------ > > Key: JBTIS-487 > URL: https://issues.jboss.org/browse/JBTIS-487 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: IS-projects-using-old-license.png, IS-projects-using-old-license_2.png > > > Please make sure that SwitchYard is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_use_license_features.adoc -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 22:54:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 22:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116698#comment-13116698 ] Nick Boldt commented on JBTIS-482: ---------------------------------- Looks like the SwitchYard features were not actually updated. See comments here: https://issues.jboss.org/browse/JBTIS-487?focusedCommentId=13116697&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13116697 > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_use_license_features.adoc > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.CR1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.CR1%22%29%29+AND+labels+%3D+task] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_use_license_features.adoc#verify-your-changes -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 22:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 22:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-487) SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116697#comment-13116697 ] Nick Boldt edited comment on JBTIS-487 at 10/8/15 10:54 PM: ------------------------------------------------------------ When I look at the latest JBT IS 4.3. Alpha2 / JBDS IS 9.0.0.Alpha2 bits I see this: * in JBT: !IS-projects-using-old-license.png! * in JBDS: !IS-projects-using-old-license_2.png! is this because you didn't publish your newer bits into the IS composites/aggregates? Or is the problem in SwitchYard itself? What's the latest version available w/ the fixed features / license terms? Something newer than 2.1.0.v20150821-1353-H598-Alpha1 ? was (Author: nickboldt): Don't mean to piss in your cornflakes, but when I look at the latest JBT IS 4.3. Alpha2 / JBDS IS 9.0.0.Alpha2 bits I see this: * in JBT: !IS-projects-using-old-license.png! * in JBDS: !IS-projects-using-old-license_2.png! is this because you didn't publish your newer bits into the IS? Or is the problem in SwitchYard itself? What's the latest version available w/ the fixed features / license terms? > SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------------ > > Key: JBTIS-487 > URL: https://issues.jboss.org/browse/JBTIS-487 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: IS-projects-using-old-license.png, IS-projects-using-old-license_2.png > > > Please make sure that SwitchYard is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_use_license_features.adoc -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 22:58:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 22:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116699#comment-13116699 ] Nick Boldt commented on JBTIS-504: ---------------------------------- BTW, I see only some projects have moved to the new license terms. Looks a bit strange when you're installing everything and have to accept two slightly different licenses. See: https://issues.jboss.org/browse/JBTIS-487?focusedCommentId=13116697&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13116697 > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 23:01:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 23:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116700#comment-13116700 ] Nick Boldt commented on JBTIS-508: ---------------------------------- I see the PR is now merged. Looks good -- see additional comments/feedback in JBTIS-504: https://issues.jboss.org/browse/JBTIS-504?focusedCommentId=13116696&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13116696 > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 23:09:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 23:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116701#comment-13116701 ] Nick Boldt commented on JBTIS-504: ---------------------------------- Perhaps this is a dumb question, but I just realized that the sites you linked to above are /development/ URLs, not /staging/ ones. I would have thought you'd present staging URLs first for review, then push that content to /development/ ONCE IT WAS VETTED. Am I crazy to think that you shouldn't just push things to /development/ without first QEing them? Or did I miss the QE signoff email which preceded the release from /staging/ to /development/ ? (It's possible -- I get a lot of email.) :D cc: [~ldimaggio] [~mmalina] [~maxandersen] [~akazakov] > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 23:19:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 23:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116702#comment-13116702 ] Nick Boldt commented on JBTIS-498: ---------------------------------- Your staging sites look way better now. http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/ http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/ https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/ https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess However, I see that you're including the same contents twice, which impacts performance when loading the site. https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/compositeArtifacts.xml and https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/compositeArtifacts.xml include * https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/ * https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ and * https://devstudio.jboss.com/9.0/stable/updates/ But https://devstudio.jboss.com/9.0/stable/updates/ includes * https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/ * https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ and So you only need to include the one URL, not all three. Meanwhile, for JBTIS, you have the opposite problem. You only include JBT, but not the JBT TP. This may impact a user's ability to install something. So instead of including http://download.jboss.org/jbosstools/mars/development/updates/core/ you should be using http://download.jboss.org/jbosstools/mars/development/updates/ (or really, the *STABLE* site http://download.jboss.org/jbosstools/mars/stable/updates/ since we went GA this week). Hope that helps! > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 23:50:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 23:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116704#comment-13116704 ] Nick Boldt commented on JBDS-3525: ---------------------------------- OK so I've found a workflow that seems to work. 1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ ) 2. Install Arquillian 1.2.0.CR1 from https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/ 3. After install & restart of JBDS, go to Window > Preferences > Install/Update > Available Software Sites and delete or disable the above CR1 site. Leave only the https://devstudio.redhat.com/9.0/stable/updates/ site enabled. (this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1. There's another way to achieve this using -D flags but it requires more cold starts of JBDS.) 4. Now fire up Central and look for Arquillian. Yep, it's unavailable. 5. So, check the box for *Enable Early Access*. Still unavailable? 6. Now, check the box for *Show installed*. Voila! It's available and installable. Alternate method (didn't try this but it should work if you don't like the above method): 1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ ) 2. Add these to your jbdevstudio.ini or use them on the commandline when launching JBDS: {code} -Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/devstudio-directory.xml -Djboss.discovery.site.url=https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/ -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/{code} 3. Install Arquillian 1.2.0.CR1 from Central using the -D flag settings above. 4. Instead of restarting when prompted, shut down JBDS and remove the above -D flags to revert to normal /stable/ settings and to see the latest updates from JBDS 9.0.0.CR1 -> GA. 5. Now fire up Central and look for Arquillian. Yep, it's unavailable. 6. So, check the box for *Enable Early Access*. Still unavailable? 7. Now, check the box for *Show installed*. Voila! It's available and installable. This feels like a workflow bug since you shouldn't be notified of available updates, but then have Central hide those updates from you until you explicitly *Show installed*. [~mickael_istria] [~fbricon] [~akazakov] WDYT? Something we should change in JBDS 9.x? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 23:57:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 8 Oct 2015 23:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116705#comment-13116705 ] Nick Boldt commented on JBDS-3525: ---------------------------------- Curiously, once I've checked Arquillian in Central to be installed, the EA site appears in the list of available software sites. So even if I then don't complete the installation, I can Help > Check for updates and JBDS will find the 1.2.0.Final version of Arquillian and can install it for me. So again, this seems like a bug. Should we: a) add the EA content into the same URL as https://devstudio.redhat.com/9.0/stable/updates/ so it's already available OOTB? No, because then a user might Help > Install New Software and install something from the EA site w/o realizing it's EA. They could have EA disabled and still do the install this way. b) add the EA URL by default into the list of Available Update Sites so it's available & enabled OOTB? Maybe - at least that way it's clear that Arquillian and other EA content comes from the EA site, not the main *supported* one. c) figure out a way for the Help > Check for updates to hit the same URL(s) that back JBT/JBDS Central, JBT/JBDS EA, and also the IS URLs too? Yeah, but the only thing I can think of here to achieve this is (a) and (b). Can't see how Check for updates can ping *hidden* URLs that are obfuscated behind Central w/o them simply being listed in the Available Software Sites listing. Thoughts? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 01:20:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Fri, 9 Oct 2015 01:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116713#comment-13116713 ] Supriya Bharadwaj commented on TOOLSDOC-684: -------------------------------------------- I'll keep that in mind. Thanks for publishing the guide, [~mhusnain]. > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 03:04:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Fri, 9 Oct 2015 03:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: Jan Richter created JBDS-3539: --------------------------------- Summary: Installer UI does not scale on Windows (10) Key: JBDS-3539 URL: https://issues.jboss.org/browse/JBDS-3539 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.0.0.GA Environment: Windows 10 9.0.0.GA installer Reporter: Jan Richter Attachments: 4kInstaller.png I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. Looks like this: !4kInstaller.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 03:15:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Fri, 9 Oct 2015 03:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBDS-3539: ------------------------------ Description: I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. Looks like this: !4kInstaller.png|thumbnail! Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. was: I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. Looks like this: !4kInstaller.png|thumbnail! > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Attachments: 4kInstaller.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 03:39:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 03:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3539: -------------------------------- Component/s: upstream > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Attachments: 4kInstaller.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 03:41:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 03:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116743#comment-13116743 ] Denis Golovin commented on JBDS-3539: ------------------------------------- That could be L&F related issue. Installer uses custom L&F that seems do not understand DPI settings on windows. > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Fix For: 9.1.0.GA > > Attachments: 4kInstaller.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 03:41:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 03:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3539: -------------------------------- Fix Version/s: 9.1.0.GA > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Fix For: 9.1.0.GA > > Attachments: 4kInstaller.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 04:36:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Fri, 9 Oct 2015 04:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj resolved TOOLSDOC-684. ---------------------------------------- Resolution: Done Guide published on Customer Portal at https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio/9.0/html/Install_Red_Hat_JBoss_Developer_Studio/index.html > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 04:39:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Fri, 9 Oct 2015 04:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-684) JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116713#comment-13116713 ] Supriya Bharadwaj edited comment on TOOLSDOC-684 at 10/9/15 4:38 AM: --------------------------------------------------------------------- I'll make a note of that, Misha. Thanks for publishing the guide, [~mhusnain]. was (Author: supriya.bharadwaj): I'll keep that in mind. Thanks for publishing the guide, [~mhusnain]. > JBDS 9: Remove mentions and screenshots with Beta or CR from the Install Guide > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-684 > URL: https://issues.jboss.org/browse/TOOLSDOC-684 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Guide, Install > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 06:45:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 9 Oct 2015 06:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3540) Developer Test - Ken and Max's epic adventure In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBDS-3540: ----------------------------------------- Summary: Developer Test - Ken and Max's epic adventure Key: JBDS-3540 URL: https://issues.jboss.org/browse/JBDS-3540 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Reporter: Max Rydahl Andersen -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 06:47:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 9 Oct 2015 06:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3541) ignore - test of jbds adventure In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBDS-3541: ----------------------------------------- Summary: ignore - test of jbds adventure Key: JBDS-3541 URL: https://issues.jboss.org/browse/JBDS-3541 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Reporter: Max Rydahl Andersen -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 06:48:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 9 Oct 2015 06:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3540) Developer Test - Ken and Max's epic adventure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3540: -------------------------------------- Story Points: 10 > Developer Test - Ken and Max's epic adventure > --------------------------------------------- > > Key: JBDS-3540 > URL: https://issues.jboss.org/browse/JBDS-3540 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Reporter: Max Rydahl Andersen > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 06:51:02 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 9 Oct 2015 06:51:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3540) Developer Test - Ken and Max's epic adventure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3540: -------------------------------------- Epic Name: Developer Test - Ken and Max's epic adventure Due Date: 1/Nov/15 > Developer Test - Ken and Max's epic adventure > --------------------------------------------- > > Key: JBDS-3540 > URL: https://issues.jboss.org/browse/JBDS-3540 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Reporter: Max Rydahl Andersen > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 07:00:01 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Fri, 9 Oct 2015 07:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBDS-3539: ------------------------------ Attachment: step6.png step5.png step4.png step3.png step2.png step9.png step8.png step7.png I've uploaded screenshots of the individual pages so that you can clearly see what the weird scaling produces. > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Fix For: 9.1.0.GA > > Attachments: 4kInstaller.png, step2.png, step3.png, step4.png, step5.png, step6.png, step7.png, step8.png, step9.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 07:13:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Fri, 9 Oct 2015 07:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-514) Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-514: --------------------------------------- Summary: Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central Key: JBTIS-514 URL: https://issues.jboss.org/browse/JBTIS-514 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 4.3.0.Alpha2 Environment: jee-mars-1 Reporter: Andrej Podhradsky Priority: Minor After installing BYOE into Eclipse Mars JEE and installing integration tools I got the following error in Error Log Unknown category 'org.jboss.tools.discovery.certification.supported' referenced by connector 'org.jboss.runtime.drools.detector.feature' declared in org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20151006_1928_B438.jar_7070743946524519340.jar The eclipse instance was run as follows {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/earlyaccess {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 07:28:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 9 Oct 2015 07:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20834) Fix issues with styled label providers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20834: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > Fix issues with styled label providers > -------------------------------------- > > Key: JBIDE-20834 > URL: https://issues.jboss.org/browse/JBIDE-20834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Snjezana Peco > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > > Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 has been fixed, we can remove the workaround related to styled label providers. > The fix is included in Mars 4.5.1 (Mars.1) and Neon 4.6.0M2. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 08:17:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Fri, 9 Oct 2015 08:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3542) Splash screen scaling is broken on Windows In-Reply-To: References: Message-ID: Jan Richter created JBDS-3542: --------------------------------- Summary: Splash screen scaling is broken on Windows Key: JBDS-3542 URL: https://issues.jboss.org/browse/JBDS-3542 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 9.0.0.GA Environment: Windows 10 4k resolution with 250% scale Reporter: Jan Richter Attachments: splash.png The splash screen window itself doesn't scale, but some text inside it does. The result looks like this: !splash.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 08:25:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 9 Oct 2015 08:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20929) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: Ilya Buziuk created JBIDE-20929: ----------------------------------- Summary: "Bower Update" shortcut does nothing when launched from editor with open bower.json Key: JBIDE-20929 URL: https://issues.jboss.org/browse/JBIDE-20929 Project: Tools (JBoss Tools) Issue Type: Bug Components: javascript-bower Affects Versions: 4.3.0.Final Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 08:28:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 9 Oct 2015 08:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20929) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20929: -------------------------------- Description: Steps to reproduce; 1) create bower.json via New -> Bower Init wizard 2) right click on the Editor with newly created bower.json file 3) Run As -> Bower Update ERROR: Nothing happens / external process was not launched > "Bower Update" shortcut does nothing when launched from editor with open bower.json > ----------------------------------------------------------------------------------- > > Key: JBIDE-20929 > URL: https://issues.jboss.org/browse/JBIDE-20929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Steps to reproduce; > 1) create bower.json via New -> Bower Init wizard > 2) right click on the Editor with newly created bower.json file > 3) Run As -> Bower Update > ERROR: Nothing happens / external process was not launched -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 09:04:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Fri, 9 Oct 2015 09:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20930) Marketplace entry for JBT says it is for "Eclipse Luna" for every version In-Reply-To: References: Message-ID: Jan Richter created JBIDE-20930: ----------------------------------- Summary: Marketplace entry for JBT says it is for "Eclipse Luna" for every version Key: JBIDE-20930 URL: https://issues.jboss.org/browse/JBIDE-20930 Project: Tools (JBoss Tools) Issue Type: Bug Components: marketplace Reporter: Jan Richter Priority: Minor JBT marketplace entry says this: "JBoss Tools is an umbrella project for a set of Eclipse Luna plugins." And since there is only one entry for all available versions, it says that every time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 09:05:01 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Fri, 9 Oct 2015 09:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20930) Marketplace entry for JBT says it is for "Eclipse Luna" for every version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBIDE-20930: -------------------------------- Affects Version/s: 4.3.0.Final > Marketplace entry for JBT says it is for "Eclipse Luna" for every version > ------------------------------------------------------------------------- > > Key: JBIDE-20930 > URL: https://issues.jboss.org/browse/JBIDE-20930 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Priority: Minor > > JBT marketplace entry says this: "JBoss Tools is an umbrella project for a set of Eclipse Luna plugins." And since there is only one entry for all available versions, it says that every time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 09:27:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 9 Oct 2015 09:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-514) Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-514: -------------------------------- Assignee: Paul Leacu > Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central > ------------------------------------------------------------------------------------------------- > > Key: JBTIS-514 > URL: https://issues.jboss.org/browse/JBTIS-514 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Environment: jee-mars-1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > After installing BYOE into Eclipse Mars JEE and installing integration tools I got the following error in Error Log > Unknown category 'org.jboss.tools.discovery.certification.supported' referenced by connector 'org.jboss.runtime.drools.detector.feature' declared in org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20151006_1928_B438.jar_7070743946524519340.jar > The eclipse instance was run as follows > {code} > ./eclipse -vmargs \ > -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ > -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery \ > -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/earlyaccess > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 09:37:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 9 Oct 2015 09:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20795: ---------------------------------- Fix Version/s: 4.3.1.Final (was: 4.4.0.Alpha1) > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.1.Final > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 09:37:01 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 9 Oct 2015 09:37:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco resolved JBIDE-20795. ----------------------------------- Resolution: Done The fix has also been applied to the jbosstools-4.3.x branch. > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.1.Final > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 10:14:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 9 Oct 2015 10:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117022#comment-13117022 ] Paul Leacu commented on JBTIS-504: ---------------------------------- [~nickboldt] - Thanks for the review. * I've corrected the aesthetics by tweeking the composite repository names to be more consistent. * http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml is corrected to contain the JBT EA plugin * https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml and https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/devstudio-directory.xml are corrected to contain the JBDS EA plugin. * The IS plugins have been fully vetted by QE. I had QE do a quick smoke test of the IS discovery changes last night. I still need to go through my Jenkins jobs and optimize/ clean up. I could ask QE to go though another smoke test of what's there now. I think if you're okay with the current structure we can go live now. cc: [~ldimaggio] [~mmalina] [~maxandersen] [~akazakov] > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 11:24:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Fri, 9 Oct 2015 11:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20446) Hibernate 5.0 support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers updated JBIDE-20446: ------------------------------ Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) > Hibernate 5.0 support > --------------------- > > Key: JBIDE-20446 > URL: https://issues.jboss.org/browse/JBIDE-20446 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > > Hibernate 5.0 is close to be released (CR4 at the time of writing this JIRA). JBoss Tools Hibernate Tools should support this latest version. Would be good to have it in JBDS 9.0.GA at least in form of early access or experimental feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 11:44:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 11:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117072#comment-13117072 ] Alexey Kazakov commented on JBDS-3525: -------------------------------------- If there is no EA site listed in available update sites why this notification of a new available Arquilian appears? Btw I just tried your: {quote} 1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ ) 2. Install Arquillian 1.2.0.CR1 from https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/ 3. After install & restart of JBDS, go to Window > Preferences > Install/Update > Available Software Sites and delete or disable the above CR1 site. Leave only the https://devstudio.redhat.com/9.0/stable/updates/ site enabled. (this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1. There's another way to achieve this using -D flags but it requires more cold starts of JBDS.) 4. Now fire up Central and look for Arquillian. Yep, it's unavailable. 5. So, check the box for Enable Early Access. Still unavailable? 6. Now, check the box for Show installed. Voila! It's available and installable. {quote} But instead of #4 I just checked for updates and successfully updated Arquillian CR1 to Final having the only http://download.jboss.org/jbosstools/mars/snapshots/updates/ enabled. Where did it come from? I thought it works in that way: 1. When you check Enable EA in central then the EA discovery update site is added to the list of available and enabled update sites. So you can install EA content from it. 2. When you uncheck EA then its site removed from the list. But it's differently much more complicated. Can you explain me how it currently works actually? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 11:45:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 11:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117072#comment-13117072 ] Alexey Kazakov edited comment on JBDS-3525 at 10/9/15 11:44 AM: ---------------------------------------------------------------- If there is no EA site listed in available update sites why this notification of a new available Arquilian appears? Btw I just tried your: {quote} 1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ ) 2. Install Arquillian 1.2.0.CR1 from https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/ 3. After install & restart of JBDS, go to Window > Preferences > Install/Update > Available Software Sites and delete or disable the above CR1 site. Leave only the https://devstudio.redhat.com/9.0/stable/updates/ site enabled. (this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1. There's another way to achieve this using -D flags but it requires more cold starts of JBDS.) 4. Now fire up Central and look for Arquillian. Yep, it's unavailable. 5. So, check the box for Enable Early Access. Still unavailable? 6. Now, check the box for Show installed. Voila! It's available and installable. {quote} But instead of #4 I just checked for updates and successfully updated Arquillian CR1 to Final having the only http://download.jboss.org/jbosstools/mars/snapshots/updates/ enabled. Where did it come from? I thought it works in that way: 1. When you check Enable EA in central then the EA discovery update site is added to the list of available and enabled update sites. So you can install EA content from it. 2. When you uncheck EA then its site removed from the list. But it's definitely much more complicated. Can you explain me how it currently works actually? was (Author: akazakov): If there is no EA site listed in available update sites why this notification of a new available Arquilian appears? Btw I just tried your: {quote} 1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ ) 2. Install Arquillian 1.2.0.CR1 from https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/ 3. After install & restart of JBDS, go to Window > Preferences > Install/Update > Available Software Sites and delete or disable the above CR1 site. Leave only the https://devstudio.redhat.com/9.0/stable/updates/ site enabled. (this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1. There's another way to achieve this using -D flags but it requires more cold starts of JBDS.) 4. Now fire up Central and look for Arquillian. Yep, it's unavailable. 5. So, check the box for Enable Early Access. Still unavailable? 6. Now, check the box for Show installed. Voila! It's available and installable. {quote} But instead of #4 I just checked for updates and successfully updated Arquillian CR1 to Final having the only http://download.jboss.org/jbosstools/mars/snapshots/updates/ enabled. Where did it come from? I thought it works in that way: 1. When you check Enable EA in central then the EA discovery update site is added to the list of available and enabled update sites. So you can install EA content from it. 2. When you uncheck EA then its site removed from the list. But it's differently much more complicated. Can you explain me how it currently works actually? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 11:51:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 11:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3525: ----------------------------- Attachment: arquillian-in-jbt.png {quote}But instead of #4 I just checked for updates and successfully updated Arquillian CR1 to Final having the only http://download.jboss.org/jbosstools/mars/snapshots/updates/ enabled. Where did it come from?{quote} Arquillian isn't Early Access in JBoss Tools, only in JBDS. So it came from http://download.jboss.org/jbosstools/mars/snapshots/updates/ because it's part of that site: !arquillian-in-jbt.png! This is strictly a JBDS issue, unless we can prove a similar problem exists for the `angularjs-eclipse-feature` connector in JBT EA [1]. [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools/org.jboss.tools.central.discovery.earlyaccess/plugin.xml#L29-L50 > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 11:59:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Fri, 9 Oct 2015 11:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20931) Build error on: jbosstools-browsersim In-Reply-To: References: Message-ID: Len DiMaggio created JBIDE-20931: ------------------------------------ Summary: Build error on: jbosstools-browsersim Key: JBIDE-20931 URL: https://issues.jboss.org/browse/JBIDE-20931 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Affects Versions: 4.3.0.Final Reporter: Len DiMaggio Steps to recreate: git clone git at github.com:jbosstools/jbosstools-browsersim.git cd jbosstools-browsersim/ mvn clean install -------------------------------------------------------- mvn clean install [INFO] Scanning for projects... [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-jst (${jbosstools-jst-site}): No connector available to access repository jbosstools-jst (${jbosstools-jst-site}) of type p2 using the available factories WagonRepositoryConnectorFactory [INFO] Computing target platform for MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-base_master [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-jst_master [INFO] Resolving dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.0.qualifier requires 'bundle org.eclipse.jetty.server [9.2.13,9.2.14)' but it could not be found [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier depends on: bundle org.jboss.tools.browsersim.ui 3.7.0 [ERROR] [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml: See log for details -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 11:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 11:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117084#comment-13117084 ] Alexey Kazakov commented on JBTIS-504: -------------------------------------- Guys, we need to fix this problem with multiple IS N/A connectors in Central ASAP. I can't verify your solutions right now, but please go ahead and do what is needed to fix this problem ASAP. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:00:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBTIS-504: --------------------------------- Priority: Critical (was: Major) > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:02:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 12:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117087#comment-13117087 ] Nick Boldt commented on JBTIS-504: ---------------------------------- OK, so because QE signed off on everything, it makes sense to have this in /staging/ and /development/ too. (It's not all in /staging/, which surprises me since I would hope your workflow is to STAGE things first, the COPY that content to /development/.) But that said, my tests last night showed the correct IS content showing up in Central (other than the composite*.xml site labels and missing JBDS EA stuff). +1 to link your 4 new plugins into here to make them live (as well as copying them onto the server in the plugins/ folders): http://download.jboss.org/jbosstools/mars/development/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.GA/devstudio-directory.xml http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/devstudio-directory.xml > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 12:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117088#comment-13117088 ] Nick Boldt commented on JBTIS-508: ---------------------------------- Just found some rogue content in http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/jbosstools-directory.xml (incomplete and non-functional XML) and http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/plugins/ (had the old B430 version in there) Not sure how it got there (might be my fault, unsure) but I've deleted it. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3539: ------------------------------------ Assignee: Denis Golovin Yes, it looks ugly :-( We should investigate what we can do here. > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 9.1.0.GA > > Attachments: 4kInstaller.png, step2.png, step3.png, step4.png, step5.png, step6.png, step7.png, step8.png, step9.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3539: --------------------------------- Fix Version/s: 9.0.1.GA > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 9.1.0.GA > > Attachments: 4kInstaller.png, step2.png, step3.png, step4.png, step5.png, step6.png, step7.png, step8.png, step9.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:10:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3539: --------------------------------- Fix Version/s: 10.0.0.Alpha1 > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 9.1.0.GA, 10.0.0.Alpha1 > > Attachments: 4kInstaller.png, step2.png, step3.png, step4.png, step5.png, step6.png, step7.png, step8.png, step9.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:18:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20929) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20929: ----------------------------------- Fix Version/s: 4.3.1.Final > "Bower Update" shortcut does nothing when launched from editor with open bower.json > ----------------------------------------------------------------------------------- > > Key: JBIDE-20929 > URL: https://issues.jboss.org/browse/JBIDE-20929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > Steps to reproduce; > 1) create bower.json via New -> Bower Init wizard > 2) right click on the Editor with newly created bower.json file > 3) Run As -> Bower Update > ERROR: Nothing happens / external process was not launched -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:18:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20929) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117093#comment-13117093 ] Alexey Kazakov commented on JBIDE-20929: ---------------------------------------- We should fix it for 4.3.x too. > "Bower Update" shortcut does nothing when launched from editor with open bower.json > ----------------------------------------------------------------------------------- > > Key: JBIDE-20929 > URL: https://issues.jboss.org/browse/JBIDE-20929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > Steps to reproduce; > 1) create bower.json via New -> Bower Init wizard > 2) right click on the Editor with newly created bower.json file > 3) Run As -> Bower Update > ERROR: Nothing happens / external process was not launched -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:25:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Fri, 9 Oct 2015 12:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20931) Build error on: jbosstools-browsersim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117097#comment-13117097 ] Konstantin Marmalyukov commented on JBIDE-20931: ------------------------------------------------ Len, I know about it. The same will be for livereload and aerogear repos. It was caused by jetty update in tp > Build error on: jbosstools-browsersim > ------------------------------------- > > Key: JBIDE-20931 > URL: https://issues.jboss.org/browse/JBIDE-20931 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > > Steps to recreate: > git clone git at github.com:jbosstools/jbosstools-browsersim.git > cd jbosstools-browsersim/ > mvn clean install > -------------------------------------------------------- > mvn clean install > [INFO] Scanning for projects... > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-jst (${jbosstools-jst-site}): No connector available to access repository jbosstools-jst (${jbosstools-jst-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [INFO] Computing target platform for MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-base_master > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-jst_master > [INFO] Resolving dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.0.qualifier requires 'bundle org.eclipse.jetty.server [9.2.13,9.2.14)' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier depends on: bundle org.jboss.tools.browsersim.ui 3.7.0 > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml: See log for details -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20930) Marketplace entry for JBT says it is for "Eclipse Luna" for every version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20930: ----------------------------------- Priority: Major (was: Minor) > Marketplace entry for JBT says it is for "Eclipse Luna" for every version > ------------------------------------------------------------------------- > > Key: JBIDE-20930 > URL: https://issues.jboss.org/browse/JBIDE-20930 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Fix For: 4.3.1.Final > > > JBT marketplace entry says this: "JBoss Tools is an umbrella project for a set of Eclipse Luna plugins." And since there is only one entry for all available versions, it says that every time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20930) Marketplace entry for JBT says it is for "Eclipse Luna" for every version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20930: ----------------------------------- Fix Version/s: 4.3.1.Final > Marketplace entry for JBT says it is for "Eclipse Luna" for every version > ------------------------------------------------------------------------- > > Key: JBIDE-20930 > URL: https://issues.jboss.org/browse/JBIDE-20930 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Fix For: 4.3.1.Final > > > JBT marketplace entry says this: "JBoss Tools is an umbrella project for a set of Eclipse Luna plugins." And since there is only one entry for all available versions, it says that every time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20930) Marketplace entry for JBT says it is for "Eclipse Luna" for every version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20930: -------------------------------------- Assignee: Nick Boldt > Marketplace entry for JBT says it is for "Eclipse Luna" for every version > ------------------------------------------------------------------------- > > Key: JBIDE-20930 > URL: https://issues.jboss.org/browse/JBIDE-20930 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 4.3.1.Final > > > JBT marketplace entry says this: "JBoss Tools is an umbrella project for a set of Eclipse Luna plugins." And since there is only one entry for all available versions, it says that every time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:33:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20795: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:33:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20932) Fix KeyBindingsTest errors on Mac OS X In-Reply-To: References: Message-ID: Denis Golovin created JBIDE-20932: ------------------------------------- Summary: Fix KeyBindingsTest errors on Mac OS X Key: JBIDE-20932 URL: https://issues.jboss.org/browse/JBIDE-20932 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html-source-editing Affects Versions: 4.4.0.Alpha1 Environment: Mac OS X Reporter: Denis Golovin {code} KeyCombination[] keys = new KeyCombination[] { new KeyCombination(SWT.CTRL, 'd'), new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000002), // Arrow Down new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000001), // Arrow UP new KeyCombination(SWT.ALT, 0x1000001), new KeyCombination(SWT.ALT, 0x1000002) }; {code} Should use SWT.COMMAND instead SWT.CTRL on Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:34:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20932) Fix KeyBindingsTest errors on Mac OS X In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20932: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 > Fix KeyBindingsTest errors on Mac OS X > -------------------------------------- > > Key: JBIDE-20932 > URL: https://issues.jboss.org/browse/JBIDE-20932 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Environment: Mac OS X > Reporter: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > {code} KeyCombination[] keys = new KeyCombination[] { > new KeyCombination(SWT.CTRL, 'd'), > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000002), // Arrow Down > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000001), // Arrow UP > new KeyCombination(SWT.ALT, 0x1000001), > new KeyCombination(SWT.ALT, 0x1000002) }; > {code} > Should use SWT.COMMAND instead SWT.CTRL on Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:34:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20932) Fix KeyBindingsTest errors on Mac OS X In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin reassigned JBIDE-20932: ------------------------------------- Assignee: Denis Golovin > Fix KeyBindingsTest errors on Mac OS X > -------------------------------------- > > Key: JBIDE-20932 > URL: https://issues.jboss.org/browse/JBIDE-20932 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > {code} KeyCombination[] keys = new KeyCombination[] { > new KeyCombination(SWT.CTRL, 'd'), > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000002), // Arrow Down > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000001), // Arrow UP > new KeyCombination(SWT.ALT, 0x1000001), > new KeyCombination(SWT.ALT, 0x1000002) }; > {code} > Should use SWT.COMMAND instead SWT.CTRL on Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:34:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 12:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117103#comment-13117103 ] Nick Boldt commented on JBTIS-504: ---------------------------------- BTW [~pleacu] your composite sites (which you'll need to be working once you link to them from ide-config.properties [1]) are still wrong -- they're missing the JBT TP content. http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/compositeContent.xml http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/compositeContent.xml And these contain duplicate entries: https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/compositeArtifacts.xml https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/compositeArtifacts.xml I guess you didn't see my comments here? https://issues.jboss.org/browse/JBTIS-498?focusedCommentId=13116702&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13116702 [1] http://download.jboss.org/jbosstools/configuration/ide-config.properties > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:34:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117104#comment-13117104 ] Alexey Kazakov commented on JBIDE-20795: ---------------------------------------- Please when fixing anything in both master and 4.3.x then create a separate issue so we will have two clones for 4.3.1 and 4.4.0. It helps QE to verify the issue was fixed in both streams. > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:37:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-19532: ---------------------------------- Fix Version/s: (was: 4.3.x) > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.4.x > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png, JBIDE-19532.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:40:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-14642: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > How to automate process of bumping version for changed modules/submodules for every release > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14642 > URL: https://issues.jboss.org/browse/JBIDE-14642 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Labels: versioning > Fix For: 4.4.x > > > The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped. > We need two things: > A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing) > B) document/automate a process which every affected lead can follow to make this happen and if not See #A -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:41:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 9 Oct 2015 12:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20933) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: Snjezana Peco created JBIDE-20933: ------------------------------------- Summary: canonical form is required(project=arquillian-test) Key: JBIDE-20933 URL: https://issues.jboss.org/browse/JBIDE-20933 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: arquillian Reporter: Aslak Knutsen Assignee: Snjezana Peco Fix For: 4.3.1.Final, 4.4.0.Alpha1 This code: {code} @RunWith(Arquillian.class) public class SimpleTestCase { @Deployment public static WebArchive test() { return ShrinkWrap.create(WebArchive.class) .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); } @Test public void shouldX() {} } {code} produce the following warning: {code} null org.jboss.tools.arquillian.core Warning Wed Sep 23 23:16:17 CEST 2015 canonical form is required(project=arquillian-test) {code} On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. With a little digging it's due to the resolve("") failing since the String input is not in the correct format. The warning is marked on the Method line, not on the line where the Resolver is called. Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:41:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 9 Oct 2015 12:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20933) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20933: ---------------------------------- Fix Version/s: (was: 4.3.1.Final) > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20933 > URL: https://issues.jboss.org/browse/JBIDE-20933 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:42:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-1886) Include Seam, JSF and Struts documentation plugins in the build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin closed JBIDE-1886. -------------------------------- Fix Version/s: (was: 4.3.x) Resolution: Out of Date > Include Seam, JSF and Struts documentation plugins in the build > --------------------------------------------------------------- > > Key: JBIDE-1886 > URL: https://issues.jboss.org/browse/JBIDE-1886 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: help > Affects Versions: 2.1.0.CR1, 3.1.0.M1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:42:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-3892) Increase JUnit test's coverage up to 60% In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-3892: --------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Increase JUnit test's coverage up to 60% > ---------------------------------------- > > Key: JBIDE-3892 > URL: https://issues.jboss.org/browse/JBIDE-3892 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 3.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.x > > > to be continued for next milestone -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:46:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 9 Oct 2015 12:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20795: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.1.Final > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:48:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- Fix Version/s: 9.0.x > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.x, 9.x > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:48:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- Fix Version/s: 9.x > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.x, 9.x > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:49:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 9 Oct 2015 12:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20933) CLONE - canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20933: ---------------------------------- Summary: CLONE - canonical form is required(project=arquillian-test) (was: canonical form is required(project=arquillian-test)) > CLONE - canonical form is required(project=arquillian-test) > ----------------------------------------------------------- > > Key: JBIDE-20933 > URL: https://issues.jboss.org/browse/JBIDE-20933 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:50:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 9 Oct 2015 12:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20933) CLONE - canonical form is required(project=arquillian-test) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco resolved JBIDE-20933. ----------------------------------- Resolution: Done > CLONE - canonical form is required(project=arquillian-test) > ----------------------------------------------------------- > > Key: JBIDE-20933 > URL: https://issues.jboss.org/browse/JBIDE-20933 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:52:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-15148) CLONE - VPE-Remove Visual/Source Tab and Preview Tab on 64-bit OSs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-15148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-15148: ---------------------------------- Fix Version/s: 4.3.0.Final (was: 4.3.x) > CLONE - VPE-Remove Visual/Source Tab and Preview Tab on 64-bit OSs > ------------------------------------------------------------------ > > Key: JBIDE-15148 > URL: https://issues.jboss.org/browse/JBIDE-15148 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Environment: 64-bit > Reporter: Burr Sutter > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.0.Final > > Attachments: jbide10711-v2.patch, jbide10711.patch, Screen Shot 2012-01-25 at 11.25.49 AM.png, Screen Shot 2012-01-25 at 11.25.59 AM.png > > > *Cloned description:* > Currently the end-user is presented with > Could not open the Visual Page Editor: > Current platform 'cocoa.macosx.x86_64' is not supported. > There is no need to tease the user if the features are not available, hide the tabs. > *Update:* > * Now there is only one tab on 64-bit Mac. > * On 64-bit Windows there are three tabs, visual parts show the following message: > bq. Visual Page Editor has experimental support for Windows 64-bit. Follow the link below to get details on how to install. Until then you can click on the Source tab to hide this error/info message. [Also see VPE FAQ|https://community.jboss.org/docs/DOC-10862] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:52:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-15148) CLONE - VPE-Remove Visual/Source Tab and Preview Tab on 64-bit OSs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-15148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin closed JBIDE-15148. --------------------------------- Resolution: Done > CLONE - VPE-Remove Visual/Source Tab and Preview Tab on 64-bit OSs > ------------------------------------------------------------------ > > Key: JBIDE-15148 > URL: https://issues.jboss.org/browse/JBIDE-15148 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Environment: 64-bit > Reporter: Burr Sutter > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.0.Final > > Attachments: jbide10711-v2.patch, jbide10711.patch, Screen Shot 2012-01-25 at 11.25.49 AM.png, Screen Shot 2012-01-25 at 11.25.59 AM.png > > > *Cloned description:* > Currently the end-user is presented with > Could not open the Visual Page Editor: > Current platform 'cocoa.macosx.x86_64' is not supported. > There is no need to tease the user if the features are not available, hide the tabs. > *Update:* > * Now there is only one tab on 64-bit Mac. > * On 64-bit Windows there are three tabs, visual parts show the following message: > bq. Visual Page Editor has experimental support for Windows 64-bit. Follow the link below to get details on how to install. Until then you can click on the Source tab to hide this error/info message. [Also see VPE FAQ|https://community.jboss.org/docs/DOC-10862] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:54:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-19590: ---------------------------------- Fix Version/s: (was: 4.3.x) > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.x > > Attachments: hibernate-psf-import.mp4, oomph-installer-hibernate-codebase.png > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20918: ----------------------------------- Priority: Blocker (was: Major) > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20931) Build error on: jbosstools-browsersim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20931. ------------------------------------ Fix Version/s: 4.4.0.Alpha1 Assignee: Konstantin Marmalyukov Resolution: Duplicate Issue Duplicates JBIDE-20918 > Build error on: jbosstools-browsersim > ------------------------------------- > > Key: JBIDE-20931 > URL: https://issues.jboss.org/browse/JBIDE-20931 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.4.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > Steps to recreate: > git clone git at github.com:jbosstools/jbosstools-browsersim.git > cd jbosstools-browsersim/ > mvn clean install > -------------------------------------------------------- > mvn clean install > [INFO] Scanning for projects... > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-jst (${jbosstools-jst-site}): No connector available to access repository jbosstools-jst (${jbosstools-jst-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [INFO] Computing target platform for MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-base_master > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-jst_master > [INFO] Resolving dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.0.qualifier requires 'bundle org.eclipse.jetty.server [9.2.13,9.2.14)' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier depends on: bundle org.jboss.tools.browsersim.ui 3.7.0 > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml: See log for details -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 12:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 12:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20931) Build error on: jbosstools-browsersim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20931: ----------------------------------- Affects Version/s: 4.4.0.Alpha1 (was: 4.3.0.Final) > Build error on: jbosstools-browsersim > ------------------------------------- > > Key: JBIDE-20931 > URL: https://issues.jboss.org/browse/JBIDE-20931 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.4.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > Steps to recreate: > git clone git at github.com:jbosstools/jbosstools-browsersim.git > cd jbosstools-browsersim/ > mvn clean install > -------------------------------------------------------- > mvn clean install > [INFO] Scanning for projects... > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-jst (${jbosstools-jst-site}): No connector available to access repository jbosstools-jst (${jbosstools-jst-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [INFO] Computing target platform for MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-base_master > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-jst_master > [INFO] Resolving dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.0.qualifier requires 'bundle org.eclipse.jetty.server [9.2.13,9.2.14)' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier depends on: bundle org.jboss.tools.browsersim.ui 3.7.0 > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml: See log for details -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 14:10:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 14:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117130#comment-13117130 ] Alexey Kazakov commented on JBDS-3525: -------------------------------------- OK. I don't know why my JBDS had this JBT update site. It was some CR1 nightly build.. Anyway just downloaded JBDS 9.CR1 and it has the correct JBDS updates site. But why [~manaRH] got a notification about Arquillian update then? [~manaRH] could you please list all available and enabled sites form Preferences->Install/Update->Available Software Sites? Regarding this problem with not being able to update installed EA stuff unless check show installed in Central or adding EA site in Preferences.. why don't add an enabled EA site if user check EA in Central? User check EA, we add its site to Eclipse so it become available for installing/updating outside of Central. WDYT? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 15:28:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 15:28:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20913) Knowledge Base validation preference is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20913: ----------------------------------- Summary: Knowledge Base validation preference is ignored (was: Knowledge Base validation preference is ingnored) > Knowledge Base validation preference is ignored > ----------------------------------------------- > > Key: JBIDE-20913 > URL: https://issues.jboss.org/browse/JBIDE-20913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > 1. Create two java project, Project1 and Project2 > 2. Project1 depends on Project2 > 3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base) > 4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2. > 5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator > 6. Uncheck Enable Validation > 7. Clean/rebuild Project1 > 8. FAILURE: The warning is still there > If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears. > It looks like when we disable the KB validator at all then the old warning is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 16:11:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 16:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117155#comment-13117155 ] Denis Golovin commented on JBDS-3535: ------------------------------------- Updating to El Capitan to debug > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.x, 9.x > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 16:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 16:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117165#comment-13117165 ] Nick Boldt commented on JBTIS-498: ---------------------------------- http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/ and http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess now contain the correct content. Next up: JBDS sites. > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 17:35:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 9 Oct 2015 17:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20837) HTML5 Tabbed Properties View Problems In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117178#comment-13117178 ] Alexey Kazakov commented on JBIDE-20837: ---------------------------------------- Pushed to master and 4.3.x. Please clone and resolve the issue. > HTML5 Tabbed Properties View Problems > ------------------------------------- > > Key: JBIDE-20837 > URL: https://issues.jboss.org/browse/JBIDE-20837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: HTML5_Properties_View.png, HTML5_Properties_View2.png > > > 1. Tab "All" by default has collapsed column "Name": > !HTML5_Properties_View.png! > 2. Tab "jQuery" does not take into account size of vertical scrollbar: > !HTML5_Properties_View2.png! > Test case: > 1. Install JBDS > 2. Import HTML5 Project "jboss-as-kitchensink-html5-mobile" > 3. Open index.html in Visual Page Editor > 4. Make View "Properties" active > 5. Select different tags in the editor and watch theyr properties in Properties View -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 17:37:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 17:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-498: ----------------------------- Attachment: IS-updated-composite-sites-development.png IS-updated-composite-sites-staging.png https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/ and https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/ now also contain the correct content. Also updated the STAGING sites too, so they're consistent. [^IS-updated-composite-sites-development.png] [^IS-updated-composite-sites-staging.png] But I did notice one problem after grabbing the above screenshots. Should be using http://download.jboss.org/jbosstools/mars/stable/updates/ instead of http://download.jboss.org/jbosstools/mars/development/updates/core/ ... fixing that next. > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png > > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 17:44:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 17:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-498: ----------------------------- Attachment: JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png OK, so that last glitch is fixed. But I just noticed that the JBDS IS discovery sites have BOTH Alpha2 and Beta1 TPs in them. I can't even. !JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png! > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png, JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png > > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 17:46:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 17:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117180#comment-13117180 ] Nick Boldt edited comment on JBTIS-498 at 10/9/15 5:45 PM: ----------------------------------------------------------- OK, so that last glitch is fixed. But I just noticed that the JBDS IS discovery sites have BOTH Alpha2 and Beta1 TPs in them. I can't even. !JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png! Best case it's the same content in two places (so it's a bit of a performance hit because of all the nested metadata. worst case it's conflicting TPs which might cause unexpected install behaviours. [~pleacu] [~ldimaggio] [~akazakov] Any idea how to clean this up? was (Author: nickboldt): OK, so that last glitch is fixed. But I just noticed that the JBDS IS discovery sites have BOTH Alpha2 and Beta1 TPs in them. I can't even. !JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png! > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png, JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png > > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 17:52:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 9 Oct 2015 17:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117183#comment-13117183 ] Paul Leacu commented on JBTIS-498: ---------------------------------- The JBDSIS 9.0.0.Beta1.jbds-is-target-platform is the taken from the 4.3.0.Alpha2. > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png, JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png > > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 17:54:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 9 Oct 2015 17:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117183#comment-13117183 ] Paul Leacu edited comment on JBTIS-498 at 10/9/15 5:53 PM: ----------------------------------------------------------- The JBDSIS 9.0.0.Beta1.jbds-is-target-platform is the taken from the 4.3.0.Alpha2. The TPs are fine was (Author: pleacu): The JBDSIS 9.0.0.Beta1.jbds-is-target-platform is the taken from the 4.3.0.Alpha2. > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png, JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png > > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 18:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 18:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117188#comment-13117188 ] Nick Boldt commented on JBTIS-498: ---------------------------------- OK, so for the next release, we should look at making sure that the tree structure of JBT IS and JBDS IS are the same (no dupe content) and that JBT IS EA and JBDS IS EA are the same (again, no dupe content). I realize the reason for the variation here is that JBDS IS builds as a "site + tp" all-in-one, whereas JBT IS does not. But that doesn't mean we can't get more consistent w/ artifact names, structures, etc. If you'd like a fresh JIRA for this I can open one, or we can just leave this one open for fixversion Alpha3/Beta2 (whatever you're calling your next release). > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png, JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png > > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/ > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/ > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/ > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/ > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 18:31:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 18:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- Fix Version/s: 9.0.1.GA > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 9.x > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 18:32:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 18:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- Fix Version/s: 9.1.0.GA (was: 9.x) > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 18:32:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 18:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.GA) > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:02:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 19:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- Fix Version/s: (was: 9.0.1.GA) > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:04:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 9 Oct 2015 19:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-1234: ----------------------------- > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:04:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 19:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- Status: New (was: New) Target Release: 10.0.0.GA > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:05:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 9 Oct 2015 19:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-1234: ----------------------------- > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:05:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 19:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:05:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 19:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:05:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 9 Oct 2015 19:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-1234: ----------------------------- > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:05:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 9 Oct 2015 19:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-1234: -------------------------------- > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:05:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 19:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 19:57:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 19:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1234) Installer could check OS architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-1234: -------------------------------- Attachment: Screenshot_2015-10-09_15-56-35.png > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > Attachments: Screenshot_2015-10-09_15-56-35.png > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 20:09:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 9 Oct 2015 20:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117194#comment-13117194 ] Nick Boldt commented on JBTIS-504: ---------------------------------- Shit just got real. https://github.com/jbosstools/jbosstools-download.jboss.org/commit/aac95ba06f8e50df57fbf145040f6856af1c74f8 https://github.com/jbosstools/jbosstools-download.jboss.org/commit/223e5ceaebac2dc8f4ef4bfdceae67da90ccc5cf https://github.com/jbdevstudio/jbdevstudio-website/commit/920cde0172d3cd43eca9fa899d6d48d1b2a48bc4 > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 20:51:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 20:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20932) Fix KeyBindingsTest errors on Mac OS X In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20932: ---------------------------------- Fix Version/s: 4.3.1.Final (was: 4.4.0.Alpha1) > Fix KeyBindingsTest errors on Mac OS X > -------------------------------------- > > Key: JBIDE-20932 > URL: https://issues.jboss.org/browse/JBIDE-20932 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.1.Final > > > {code} KeyCombination[] keys = new KeyCombination[] { > new KeyCombination(SWT.CTRL, 'd'), > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000002), // Arrow Down > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000001), // Arrow UP > new KeyCombination(SWT.ALT, 0x1000001), > new KeyCombination(SWT.ALT, 0x1000002) }; > {code} > Should use SWT.COMMAND instead SWT.CTRL on Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 20:51:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 9 Oct 2015 20:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20932) Fix KeyBindingsTest errors on Mac OS X In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117198#comment-13117198 ] Denis Golovin commented on JBIDE-20932: --------------------------------------- Released to 4.3.x maintenance branch. > Fix KeyBindingsTest errors on Mac OS X > -------------------------------------- > > Key: JBIDE-20932 > URL: https://issues.jboss.org/browse/JBIDE-20932 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.1.Final > > > {code} KeyCombination[] keys = new KeyCombination[] { > new KeyCombination(SWT.CTRL, 'd'), > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000002), // Arrow Down > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000001), // Arrow UP > new KeyCombination(SWT.ALT, 0x1000001), > new KeyCombination(SWT.ALT, 0x1000002) }; > {code} > Should use SWT.COMMAND instead SWT.CTRL on Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 10 11:15:00 2015 From: issues at jboss.org (Viacheslav Kabanovich (JIRA)) Date: Sat, 10 Oct 2015 11:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117212#comment-13117212 ] Viacheslav Kabanovich commented on JBIDE-20927: ----------------------------------------------- In plugin.xml of Web Kb we declare that we do not need two specific validators provided by plugins org.eclipse.jst.jsf.facelet.ui and org.eclipse.jst.jsf.ui. Web Kb plugin does not have in classpath these plugins exactly because we do not need them. What we need is to make sure that these validators are excluded _if_ they are available. Class ValidatorExtensionReader only logs these errors without throwing exception. If we want fix it anyway, there are two ways: 1) Add Eclipse JST JSF plugins to Web Kb classpath. That will sound as "gentlemen, we have invited you to our party to inform you that we do not want you at it." 2) To add Eclipse JST JSF plugins to classpath of each test plugin that depends on Web Kb - just to prevent error messages in tests. Could you suggest a better solution? > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 10 13:20:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Sat, 10 Oct 2015 13:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20921) Create tests for HibernateMappingExporterExtension classes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers resolved JBIDE-20921. ------------------------------- Resolution: Done > Create tests for HibernateMappingExporterExtension classes > ---------------------------------------------------------- > > Key: JBIDE-20921 > URL: https://issues.jboss.org/browse/JBIDE-20921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 10 13:22:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Sat, 10 Oct 2015 13:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20934) Create tests for the HibernateMappingExporter facade classes In-Reply-To: References: Message-ID: Koen Aers created JBIDE-20934: --------------------------------- Summary: Create tests for the HibernateMappingExporter facade classes Key: JBIDE-20934 URL: https://issues.jboss.org/browse/JBIDE-20934 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 10 23:27:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Sat, 10 Oct 2015 23:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117217#comment-13117217 ] Denis Golovin commented on JBIDE-20927: --------------------------------------- Considering you're saying: "What we need is to make sure that these validators are excluded if they are available", I think we should go ahead with (1) and invite them. In most real live cases devs have JBoss Tools installed into Eclipse Java EE IDE where Eclipse JST JSF is installed and test should be executed in the same or close environment. It is not necessary do add them in test classpath, we can just install additional bundles through pom.xml. > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 11 01:05:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Sun, 11 Oct 2015 01:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20927: ----------------------------------- Priority: Minor (was: Major) > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 11 01:07:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Sun, 11 Oct 2015 01:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20927: ----------------------------------- Fix Version/s: (was: 4.3.1.Final) > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 11 01:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Sun, 11 Oct 2015 01:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117219#comment-13117219 ] Alexey Kazakov commented on JBIDE-20927: ---------------------------------------- Is this error logged once when the plugin is loaded? > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 11 08:44:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Sun, 11 Oct 2015 08:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117222#comment-13117222 ] Max Rydahl Andersen commented on JBDS-3525: ------------------------------------------- Alexey, it works exactly as you describe it. enable EA adds the EA, install from it and then if run check for updates you get updates to GA and EA content. if you disable EA then EA site is removed and check for updates should not give you updates outside GA content. If we see anything different that is a bug. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 00:41:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Mon, 12 Oct 2015 00:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker updated JBIDE-20830: -------------------------------- Parent: JBIDE-20529 Issue Type: Sub-task (was: Feature Request) > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Final > > Attachments: screenshot.png > > > h2. Offending ejb-jar.xml > If you have the following {{ejb-jar.xml}}, which I got from [this Wildfly Wiki page|https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference]: > {code:xml} > > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > > > ReplyingMDB > org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB > > > destination > java:jboss/mdbtest/messageDestinationQueue > > > > > > > > DDMyDomainSFSB > myDomain > myPrincipal > > > > {code} > h2. Errors/Warnings > You'll get a few warnings: > !screenshot.png! > In the console: > {noformat} > Description Resource Path Location Type > Referenced file contains errors (jar:file:/Users/me/Applications/sts-bundle/STS.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150723-0026-B29.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /my-project/src/main/resources/META-INF line 1 XML Problem > {noformat} > h2. Related issues > * https://bugzilla.redhat.com/show_bug.cgi?id=1193543 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 00:43:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Mon, 12 Oct 2015 00:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117233#comment-13117233 ] Rob Stryker commented on JBIDE-20830: ------------------------------------- This is a follow redirects issue. Odds are very high that, even after solving it, there'll be other issues (since there are known issues with the ejb schema). {code} curl -v http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd * Hostname was NOT found in DNS cache * Trying 156.151.59.19... * Connected to java.sun.com (156.151.59.19) port 80 (#0) > GET /xml/ns/javaee/ejb-jar_3_1.xsd HTTP/1.1 > User-Agent: curl/7.37.0 > Host: java.sun.com > Accept: */* > * HTTP 1.0, assume close after body < HTTP/1.0 301 Moved Permanently < Location: http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/ejb-jar_3_1.xsd < Server: BigIP < Connection: close < Content-Length: 0 < * Closing connection 0 {code} The wildfly example could be worked around by changing the schema location from http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd to the new location, or ensuring the upstream follow-redirects patch is accepted. > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Final > > Attachments: screenshot.png > > > h2. Offending ejb-jar.xml > If you have the following {{ejb-jar.xml}}, which I got from [this Wildfly Wiki page|https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference]: > {code:xml} > > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > > > ReplyingMDB > org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB > > > destination > java:jboss/mdbtest/messageDestinationQueue > > > > > > > > DDMyDomainSFSB > myDomain > myPrincipal > > > > {code} > h2. Errors/Warnings > You'll get a few warnings: > !screenshot.png! > In the console: > {noformat} > Description Resource Path Location Type > Referenced file contains errors (jar:file:/Users/me/Applications/sts-bundle/STS.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150723-0026-B29.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /my-project/src/main/resources/META-INF line 1 XML Problem > {noformat} > h2. Related issues > * https://bugzilla.redhat.com/show_bug.cgi?id=1193543 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 00:45:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Mon, 12 Oct 2015 00:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20769) Add JBoss DV 6.2 to Download Runtimes Wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117234#comment-13117234 ] Rob Stryker commented on JBIDE-20769: ------------------------------------- I'll need to investigate. > Add JBoss DV 6.2 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-20769 > URL: https://issues.jboss.org/browse/JBIDE-20769 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.Final > > > JBoss DV 6.2 was released 5 days ago. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-852. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 00:51:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 00:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117235#comment-13117235 ] Misha Ali commented on TOOLSDOC-610: ------------------------------------ Created PR. Sorry, [~supriya.bharadwaj], I got distracted by some splash page stuff and forgot to do this earlier. > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > Attachments: hmt_config_file_icon_modified.png, hmt_firstapp.adoc, hmt_icon_modified.png > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 00:52:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 00:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-610: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-website/pull/518 > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > Attachments: hmt_config_file_icon_modified.png, hmt_firstapp.adoc, hmt_icon_modified.png > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-653) JBDS 9 Beta1: Generate Docker Article for Beta1 and Summit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-653: ------------------------------- Sprint: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > JBDS 9 Beta1: Generate Docker Article for Beta1 and Summit > ---------------------------------------------------------- > > Key: TOOLSDOC-653 > URL: https://issues.jboss.org/browse/TOOLSDOC-653 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create a docker article based on what xavier will showcase at summit for Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-672) JBDS 9.0: Document Using Git Perspective In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-672: ------------------------------- Sprint: 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > JBDS 9.0: Document Using Git Perspective > ---------------------------------------- > > Key: TOOLSDOC-672 > URL: https://issues.jboss.org/browse/TOOLSDOC-672 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Misha Ali > Assignee: Misha Ali > > Document using Git with JBDS. > 1. Determine use cases and workflow > 2. Document common workflow > 3. Add to customer portal and JBT docs (using Git in JBDS) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-562) OpenShift How To: Add final section to First OS App for viewing created app in browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-562: ------------------------------- Sprint: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec), 2014/S23 (8-Dec > 21-Dec), 2014/S24 (22-Dec > 04-Jan), 2015/S1 (05-Jan > 18-Jan), 2015/S2+3 (19-Jan > 15-Feb), 2015/S4 (16-Feb > 01-Mar), 2015/S5 (02-Mar > 15-Mar), 2015/S6 (16-Mar > 29-Mar), 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec), 2014/S23 (8-Dec > 21-Dec), 2014/S24 (22-Dec > 04-Jan), 2015/S1 (05-Jan > 18-Jan), 2015/S2+3 (19-Jan > 15-Feb), 2015/S4 (16-Feb > 01-Mar), 2015/S5 (02-Mar > 15-Mar), 2015/S6 (16-Mar > 29-Mar), 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > OpenShift How To: Add final section to First OS App for viewing created app in browser > -------------------------------------------------------------------------------------- > > Key: TOOLSDOC-562 > URL: https://issues.jboss.org/browse/TOOLSDOC-562 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > > See: http://tools.jboss.org/documentation/howto/openshift_firstapp.html > Source: https://github.com/jbosstools/jbosstools-website/blob/master/documentation/howto/openshift_firstapp.adoc > Before 'Terminology', add a new section with instructions for viewing the application in a browser. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-671) JBDS 9.0 GA: Openshift v3+Eclipse Install/Getting Started Documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-671: ------------------------------- Sprint: 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > JBDS 9.0 GA: Openshift v3+Eclipse Install/Getting Started Documentation > ----------------------------------------------------------------------- > > Key: TOOLSDOC-671 > URL: https://issues.jboss.org/browse/TOOLSDOC-671 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Len DiMaggio > Assignee: Misha Ali > > Document install/getting started information for Eclipse with OpenShift v3. QE team will help with this after Aug 17. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-609) FeedHenry: Document how to change the splash screen In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-609: ------------------------------- Sprint: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > FeedHenry: Document how to change the splash screen > --------------------------------------------------- > > Key: TOOLSDOC-609 > URL: https://issues.jboss.org/browse/TOOLSDOC-609 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: Priority1, cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch. > This will be added to an existing article, probably as a Did You Know? Item. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-662) Add edited Advanced Install Task instructions to related docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-662: ------------------------------- Sprint: 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > Add edited Advanced Install Task instructions to related docs > ------------------------------------------------------------- > > Key: TOOLSDOC-662 > URL: https://issues.jboss.org/browse/TOOLSDOC-662 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Add edited Advanced Install Task instructions to following related docs: > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/customer-portal/installer-src.manual-instructions.txt > 2. https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=38513&product=jbossdeveloperstudio&version=9.0.0+Beta1&downloadType=distributions -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-686: ------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 28-Sep >> 11-Oct 2015-JBDS/JBT) > JBDS 9 GA: Release Notes > ------------------------ > > Key: TOOLSDOC-686 > URL: https://issues.jboss.org/browse/TOOLSDOC-686 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > > Update CR1 release notes for GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-610: ------------------------------- Sprint: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > Attachments: hmt_config_file_icon_modified.png, hmt_firstapp.adoc, hmt_icon_modified.png > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-623: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT) > Add FeedHenry Information to Existing Article about Hybrid Mobile Apps > ---------------------------------------------------------------------- > > Key: TOOLSDOC-623 > URL: https://issues.jboss.org/browse/TOOLSDOC-623 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Burr Sutter > Assignee: Supriya Bharadwaj > Fix For: 4.2.3.Final > > > Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 > Description: https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-603) Openshift: Document how to push changes to an existing OS Project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-603: ------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 28-Sep >> 11-Oct 2015-JBDS/JBT) > Openshift: Document how to push changes to an existing OS Project > ----------------------------------------------------------------- > > Key: TOOLSDOC-603 > URL: https://issues.jboss.org/browse/TOOLSDOC-603 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: openshift > Fix For: 4.3.0.Final > > > Document this use case: > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:37:01 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:37:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-307: ------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT (was: 28-Sep >> 11-Oct 2015-JBDS/JBT) > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:38:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-658) JBDS-IS 8.0.2 Install Guide: Implement installation information In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-658: ------------------------------- Sprint: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > JBDS-IS 8.0.2 Install Guide: Implement installation information > --------------------------------------------------------------- > > Key: TOOLSDOC-658 > URL: https://issues.jboss.org/browse/TOOLSDOC-658 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > > [1] - > > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio_Integration_Stack/8.0/html/Install_Red_Hat_JBoss_Developer_Studio_Integration_Stack/index.html > I really find these instructions waay to complicated and since > everything is on the same level they all look equally important. > They also don't actually use the fastest way for marketplace. > Here is what I would focus on: > 1. Install into existing Eclipse: > Use > http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-integration-stack-luna > Link to #2 about Early access > 2. Install into existing JBoss Developer Studio > Use JBoss Central > Explain additional features available under Early access > 3. Other > Install/uninstall additional features from JBoss Central > Install offline: the instructions should not be different for > eclipse or devstudio. > (section 9 could be here but I would just not worry about > documenting it) > That's it. > This makes it much less complicated IMO. > Can we make that happen ? > /max -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:38:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-686: ------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT (was: 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > JBDS 9 GA: Release Notes > ------------------------ > > Key: TOOLSDOC-686 > URL: https://issues.jboss.org/browse/TOOLSDOC-686 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > Update CR1 release notes for GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:38:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Mon, 12 Oct 2015 01:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-686) JBDS 9 GA: Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali closed TOOLSDOC-686. ------------------------------ Fix Version/s: 4.3.0.Final Resolution: Done > JBDS 9 GA: Release Notes > ------------------------ > > Key: TOOLSDOC-686 > URL: https://issues.jboss.org/browse/TOOLSDOC-686 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > Update CR1 release notes for GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 01:50:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 12 Oct 2015 01:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117238#comment-13117238 ] Supriya Bharadwaj commented on TOOLSDOC-610: -------------------------------------------- No problem, Misha. Thanks for creating the PR! > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > Attachments: hmt_config_file_icon_modified.png, hmt_firstapp.adoc, hmt_icon_modified.png > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 02:32:00 2015 From: issues at jboss.org (Viacheslav Kabanovich (JIRA)) Date: Mon, 12 Oct 2015 02:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117240#comment-13117240 ] Viacheslav Kabanovich commented on JBIDE-20927: ----------------------------------------------- Yes, it is logged once when extentions for validator and exclusions are loaded. > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 02:49:00 2015 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Mon, 12 Oct 2015 02:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny updated JBDS-3525: -------------------------------- Attachment: updates-sites.xml [~akazakov] the exported update sites EA enabling/disabling works (https://devstudio.redhat.com/9.0/stable/updates/earlyaccess/ is added or removed fine) > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 03:14:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Mon, 12 Oct 2015 03:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: Jan Richter created JBIDE-20935: ----------------------------------- Summary: Central doesn't scale back after being enlarged on Windows Key: JBIDE-20935 URL: https://issues.jboss.org/browse/JBIDE-20935 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.0.Final Environment: Windows 10 Reporter: Jan Richter Attachments: central.png When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. Like so: !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 03:17:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Mon, 12 Oct 2015 03:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBIDE-20935: -------------------------------- Environment: Windows 10 250% UI scale was:Windows 10 > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Attachments: central.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:26:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 04:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-515) Errors about duplicate ESB quickstarts in Error Log In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-515: --------------------------------------- Summary: Errors about duplicate ESB quickstarts in Error Log Key: JBTIS-515 URL: https://issues.jboss.org/browse/JBTIS-515 Project: JBoss Tools Integration Stack Issue Type: Bug Components: ESB Affects Versions: 9.0.0.Alpha2 Environment: JBDS 9.0.0.GA + JBDS-IS 9.0.0.Alpha2 Reporter: Andrej Podhradsky Priority: Minor After installing ESB feature and opening the JBos Central there are errors about duplicate ESB quickstarts in the Error Log view. ESB quickstarts are available at Help > Project Examples... Note that this doesn't cause any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:26:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 04:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-515) Errors about duplicate ESB quickstarts in Error Log In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-515: ------------------------------------ Description: After installing ESB feature and opening the JBos Central there are errors about duplicate ESB quickstarts in the Error Log view. ESB quickstarts are available at Help > Project Examples... Note that this doesn't cause any problem. {code} !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 !MESSAGE Found duplicate quickstart helloworld !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 !MESSAGE Found duplicate quickstart helloworld_action !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 !MESSAGE Found duplicate quickstart helloworld_file_action !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 !MESSAGE Found duplicate quickstart webservice_consumer1 !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 !MESSAGE Found duplicate quickstart webservice_producer !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 !MESSAGE Found duplicate quickstart transform_CSV2XML !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 !MESSAGE Found duplicate quickstart transform_XML2POJO !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 !MESSAGE Found duplicate quickstart transform_XML2XML_date_manipulation !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 !MESSAGE Found duplicate quickstart transform_XML2XML_simple {code} was: After installing ESB feature and opening the JBos Central there are errors about duplicate ESB quickstarts in the Error Log view. ESB quickstarts are available at Help > Project Examples... Note that this doesn't cause any problem. > Errors about duplicate ESB quickstarts in Error Log > --------------------------------------------------- > > Key: JBTIS-515 > URL: https://issues.jboss.org/browse/JBTIS-515 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: ESB > Affects Versions: 9.0.0.Alpha2 > Environment: JBDS 9.0.0.GA + JBDS-IS 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Minor > > After installing ESB feature and opening the JBos Central there are errors about duplicate ESB quickstarts in the Error Log view. > ESB quickstarts are available at Help > Project Examples... > Note that this doesn't cause any problem. > {code} > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 > !MESSAGE Found duplicate quickstart helloworld > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 > !MESSAGE Found duplicate quickstart helloworld_action > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart helloworld_file_action > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart webservice_consumer1 > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart webservice_producer > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_CSV2XML > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2POJO > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2XML_date_manipulation > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2XML_simple > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:37:01 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 04:37:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-516) JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-516: --------------------------------------- Summary: JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS Key: JBTIS-516 URL: https://issues.jboss.org/browse/JBTIS-516 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 9.0.0.Alpha2 Reporter: Andrej Podhradsky Priority: Critical JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS. Currently, the integration stack GA contains only toolings for SOA 5.x development but this category is at the bottom (see the attache screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:37:01 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 04:37:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-516) JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-516: ------------------------------------ Attachment: jbdsis-900alpha2-categories.png > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS > ------------------------------------------------------------------ > > Key: JBTIS-516 > URL: https://issues.jboss.org/browse/JBTIS-516 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: jbdsis-900alpha2-categories.png > > > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS. Currently, the integration stack GA contains only toolings for SOA 5.x development but this category is at the bottom (see the attache screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:45:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Mon, 12 Oct 2015 04:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20936) Unable to import Fuse Integration Project from Central when Fuse isn't installed. In-Reply-To: References: Message-ID: Radim Hopp created JBIDE-20936: ---------------------------------- Summary: Unable to import Fuse Integration Project from Central when Fuse isn't installed. Key: JBIDE-20936 URL: https://issues.jboss.org/browse/JBIDE-20936 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.0.Final Environment: JBDS 9.0.0 Reporter: Radim Hopp Priority: Critical I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). This might be split to two issues: 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: {noformat} Problems occurred while performing installation: There are no connectors to install There are no connectors to install {noformat} {noformat} java.lang.IllegalArgumentException: There are no connectors to install at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) {noformat} Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:45:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Mon, 12 Oct 2015 04:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20936) Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Hopp updated JBIDE-20936: ------------------------------- Summary: Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed. (was: Unable to import Fuse Integration Project from Central when Fuse isn't installed.) > Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed. > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20936 > URL: https://issues.jboss.org/browse/JBIDE-20936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Priority: Critical > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:46:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Mon, 12 Oct 2015 04:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20920) Livereload is broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117277#comment-13117277 ] Xavier Coulon commented on JBIDE-20920: --------------------------------------- PR verified and merged. Thanks, [~kmarmaliykov] > Livereload is broken since jetty v 9.3.2 was added to TP > -------------------------------------------------------- > > Key: JBIDE-20920 > URL: https://issues.jboss.org/browse/JBIDE-20920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Livereload cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 04:59:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 04:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-517: --------------------------------------- Summary: Update web pages for JBDS-IS 9.x Key: JBTIS-517 URL: https://issues.jboss.org/browse/JBTIS-517 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 9.0.0.Alpha2 Reporter: Andrej Podhradsky Priority: Minor Update web pages for JBDS-IS 9.x at * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 05:00:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 05:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-517: ------------------------------------ Attachment: jbdsis-900alpha2-webpage.png jbdsis-900alpha2ea-webpage.png > Update web pages for JBDS-IS 9.x > -------------------------------- > > Key: JBTIS-517 > URL: https://issues.jboss.org/browse/JBTIS-517 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Minor > Attachments: jbdsis-900alpha2-webpage.png, jbdsis-900alpha2ea-webpage.png > > > Update web pages for JBDS-IS 9.x at > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ > See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 05:02:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 05:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-516) JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117284#comment-13117284 ] Andrej Podhradsky commented on JBTIS-516: ----------------------------------------- The same is for early access. > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS > ------------------------------------------------------------------ > > Key: JBTIS-516 > URL: https://issues.jboss.org/browse/JBTIS-516 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: jbdsis-900alpha2-categories.png > > > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS. Currently, the integration stack GA contains only toolings for SOA 5.x development but this category is at the bottom (see the attache screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 05:10:01 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Mon, 12 Oct 2015 05:10:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20937) Create resource(s) from json In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-20937: ------------------------------------- Summary: Create resource(s) from json Key: JBIDE-20937 URL: https://issues.jboss.org/browse/JBIDE-20937 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.CR2 Reporter: Mari?n Labuda Priority: Critical It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 05:11:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Mon, 12 Oct 2015 05:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20937) Create resource(s) from json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20937: ---------------------------------- Description: It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). was: It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Critical > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 05:33:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 12 Oct 2015 05:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-603) Openshift: Document how to push changes to an existing OS Project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj resolved TOOLSDOC-603. ---------------------------------------- Resolution: Done This has been documented at: https://access.redhat.com/articles/1610503#import_app Have also confirmed it with Marian Labuda. > Openshift: Document how to push changes to an existing OS Project > ----------------------------------------------------------------- > > Key: TOOLSDOC-603 > URL: https://issues.jboss.org/browse/TOOLSDOC-603 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: openshift > Fix For: 4.3.0.Final > > > Document this use case: > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 06:59:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 12 Oct 2015 06:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117320#comment-13117320 ] Supriya Bharadwaj commented on TOOLSDOC-307: -------------------------------------------- > Discussion with Marian about change in this functionality > Tried out steps as per he had suggested >> Created new ssh key >> Created project on https://openshift.redhat.com >> Trying to import the project into jbds; unable to do so; getting an error: "failed to read artifact description" > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 07:41:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Mon, 12 Oct 2015 07:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20938) Report proper error when blog author is unknown In-Reply-To: References: Message-ID: Xavier Coulon created JBIDE-20938: ------------------------------------- Summary: Report proper error when blog author is unknown Key: JBIDE-20938 URL: https://issues.jboss.org/browse/JBIDE-20938 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: website Affects Versions: 4.3.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.1.Final, 4.4.0.Alpha1 Building the website fails hard if a blog entry has a unknown author. There should be a proper error message instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 07:42:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 12 Oct 2015 07:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20938) Report proper error when blog author is unknown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117340#comment-13117340 ] Max Rydahl Andersen commented on JBIDE-20938: --------------------------------------------- proper error and be able to still render would be great ;) > Report proper error when blog author is unknown > ----------------------------------------------- > > Key: JBIDE-20938 > URL: https://issues.jboss.org/browse/JBIDE-20938 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > Building the website fails hard if a blog entry has a unknown author. There should be a proper error message instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 07:42:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 12 Oct 2015 07:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20938) Report proper error when blog author is unknown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117341#comment-13117341 ] Max Rydahl Andersen commented on JBIDE-20938: --------------------------------------------- ex: https://github.com/jbosstools/jbosstools-website/pull/516/files > Report proper error when blog author is unknown > ----------------------------------------------- > > Key: JBIDE-20938 > URL: https://issues.jboss.org/browse/JBIDE-20938 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > Building the website fails hard if a blog entry has a unknown author. There should be a proper error message instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 08:36:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 12 Oct 2015 08:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20939) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: Ilya Buziuk created JBIDE-20939: ----------------------------------- Summary: "Bower Update" shortcut does nothing when launched from editor with open bower.json Key: JBIDE-20939 URL: https://issues.jboss.org/browse/JBIDE-20939 Project: Tools (JBoss Tools) Issue Type: Bug Components: javascript-bower Affects Versions: 4.3.0.Final Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.3.1.Final, 4.4.0.Alpha1 Steps to reproduce; 1) create bower.json via New -> Bower Init wizard 2) right click on the Editor with newly created bower.json file 3) Run As -> Bower Update ERROR: Nothing happens / external process was not launched -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 08:37:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 12 Oct 2015 08:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20939) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20939: -------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > "Bower Update" shortcut does nothing when launched from editor with open bower.json > ----------------------------------------------------------------------------------- > > Key: JBIDE-20939 > URL: https://issues.jboss.org/browse/JBIDE-20939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > Steps to reproduce; > 1) create bower.json via New -> Bower Init wizard > 2) right click on the Editor with newly created bower.json file > 3) Run As -> Bower Update > ERROR: Nothing happens / external process was not launched -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 08:37:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 12 Oct 2015 08:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20929) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20929: -------------------------------- Fix Version/s: (was: 4.3.1.Final) > "Bower Update" shortcut does nothing when launched from editor with open bower.json > ----------------------------------------------------------------------------------- > > Key: JBIDE-20929 > URL: https://issues.jboss.org/browse/JBIDE-20929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Steps to reproduce; > 1) create bower.json via New -> Bower Init wizard > 2) right click on the Editor with newly created bower.json file > 3) Run As -> Bower Update > ERROR: Nothing happens / external process was not launched -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 08:44:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 08:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-516) JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-516. ------------------------------ Fix Version/s: 9.0.0.Alpha2 Resolution: Done Thanks for catching this Andrej - please retry. > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS > ------------------------------------------------------------------ > > Key: JBTIS-516 > URL: https://issues.jboss.org/browse/JBTIS-516 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Critical > Fix For: 9.0.0.Alpha2 > > Attachments: jbdsis-900alpha2-categories.png > > > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS. Currently, the integration stack GA contains only toolings for SOA 5.x development but this category is at the bottom (see the attache screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 08:48:00 2015 From: issues at jboss.org (Brian Fitzpatrick (JIRA)) Date: Mon, 12 Oct 2015 08:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-515) Errors about duplicate ESB quickstarts in Error Log In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117381#comment-13117381 ] Brian Fitzpatrick commented on JBTIS-515: ----------------------------------------- [~pleacu] This is very strange. The ESB examples haven't been updated in forever (https://github.com/jbosstools/jbosstools-esb/blob/master/quickstarts/jbtis-esb-project-examples-community-7.1.xml)... Is it possible they're being picked up twice in JBTIS/JBDSIS somehow? > Errors about duplicate ESB quickstarts in Error Log > --------------------------------------------------- > > Key: JBTIS-515 > URL: https://issues.jboss.org/browse/JBTIS-515 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: ESB > Affects Versions: 9.0.0.Alpha2 > Environment: JBDS 9.0.0.GA + JBDS-IS 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Minor > > After installing ESB feature and opening the JBos Central there are errors about duplicate ESB quickstarts in the Error Log view. > ESB quickstarts are available at Help > Project Examples... > Note that this doesn't cause any problem. > {code} > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 > !MESSAGE Found duplicate quickstart helloworld > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 > !MESSAGE Found duplicate quickstart helloworld_action > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart helloworld_file_action > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart webservice_consumer1 > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart webservice_producer > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_CSV2XML > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2POJO > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2XML_date_manipulation > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2XML_simple > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 09:01:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 09:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-515) Errors about duplicate ESB quickstarts in Error Log In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117385#comment-13117385 ] Paul Leacu commented on JBTIS-515: ---------------------------------- I suppose so. Lots of changes getting Mars Alpha2 working. If you can take a quick look at it first that'd be greqat - document anything you find of relevance. I'm still working on releasing Alpha2 and the Luna CR2 for this week. Thkx > Errors about duplicate ESB quickstarts in Error Log > --------------------------------------------------- > > Key: JBTIS-515 > URL: https://issues.jboss.org/browse/JBTIS-515 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: ESB > Affects Versions: 9.0.0.Alpha2 > Environment: JBDS 9.0.0.GA + JBDS-IS 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Minor > > After installing ESB feature and opening the JBos Central there are errors about duplicate ESB quickstarts in the Error Log view. > ESB quickstarts are available at Help > Project Examples... > Note that this doesn't cause any problem. > {code} > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 > !MESSAGE Found duplicate quickstart helloworld > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.667 > !MESSAGE Found duplicate quickstart helloworld_action > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart helloworld_file_action > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart webservice_consumer1 > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart webservice_producer > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_CSV2XML > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2POJO > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2XML_date_manipulation > !ENTRY org.jboss.tools.central 4 0 2015-10-12 10:09:16.668 > !MESSAGE Found duplicate quickstart transform_XML2XML_simple > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 09:08:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 09:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-518) Publish JBTIS 4.3.0.Alpha2/ JBDSIS 9.0.0.Alpha2 to jbosstools website In-Reply-To: References: Message-ID: Paul Leacu created JBTIS-518: -------------------------------- Summary: Publish JBTIS 4.3.0.Alpha2/ JBDSIS 9.0.0.Alpha2 to jbosstools website Key: JBTIS-518 URL: https://issues.jboss.org/browse/JBTIS-518 Project: JBoss Tools Integration Stack Issue Type: Feature Request Reporter: Paul Leacu Assignee: Paul Leacu Publish JBTIS 4.3.0.Alpha2/ JBDSIS 9.0.0.Alpha2 to jbosstools website -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 09:13:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 09:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-516) JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-516. ----------------------------------- Verified > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS > ------------------------------------------------------------------ > > Key: JBTIS-516 > URL: https://issues.jboss.org/browse/JBTIS-516 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Priority: Critical > Fix For: 9.0.0.Alpha2 > > Attachments: jbdsis-900alpha2-categories.png > > > JBDS-IS 9.0.0.Alpha2 update site contains all categories from JBDS. Currently, the integration stack GA contains only toolings for SOA 5.x development but this category is at the bottom (see the attache screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 09:21:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 09:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117395#comment-13117395 ] Andrej Podhradsky commented on JBDS-3537: ----------------------------------------- It seems that https://devstudio.jboss.com/ is not working anymore. Is it just temporary or was it moved to https://devstudio.redhat.com ? > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 09:31:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 12 Oct 2015 09:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-519) Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-519: --------------------------------------- Summary: Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP Key: JBTIS-519 URL: https://issues.jboss.org/browse/JBTIS-519 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 9.0.0.Alpha2 Reporter: Andrej Podhradsky Please upload JBDS-IS 9.0.0.Alpha2 zip files to CSP -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:05:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim commented on JBIDE-20764: ------------------------------------------ in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:12:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 10:11 AM: --------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:14:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 10:13 AM: --------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" (via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:23:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-19178: ------------------------------------- Summary: Explorer, Servers view: Add logical view to OpenShift v3 explorer (was: Explorer: Add logical view to OpenShift v3 explorer) > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:24:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:24:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117427#comment-13117427 ] Andre Dietisheim commented on JBIDE-19178: ------------------------------------------ In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {code} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. + Applications + Foo (the application root node; properties view might contain services and routes with actions like, open in browser) + instance-1 (an instance of the application, i.e. the container running the application) + instance-2 + OpenShift + ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: + root + Deployments + Deployment-a + pod-a + instance 1 + container 1 (properties might show the specific build) + pod-b + Services + service-a (properties view might expose related routes) + Builds + Config-a + build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {code} > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:29:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 10:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20932) Fix KeyBindingsTest errors on Mac OS X In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20932: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Fix KeyBindingsTest errors on Mac OS X > -------------------------------------- > > Key: JBIDE-20932 > URL: https://issues.jboss.org/browse/JBIDE-20932 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > {code} KeyCombination[] keys = new KeyCombination[] { > new KeyCombination(SWT.CTRL, 'd'), > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000002), // Arrow Down > new KeyCombination(SWT.CTRL | SWT.ALT, 0x1000001), // Arrow UP > new KeyCombination(SWT.ALT, 0x1000001), > new KeyCombination(SWT.ALT, 0x1000002) }; > {code} > Should use SWT.COMMAND instead SWT.CTRL on Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:36:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 10:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117437#comment-13117437 ] Alexey Kazakov commented on JBIDE-20927: ---------------------------------------- {quote} In most real live cases devs have JBoss Tools installed into Eclipse Java EE IDE where Eclipse JST JSF is installed {quote} Yes, so, in most real live cases they won't see this error in the log :) > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:38:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117427#comment-13117427 ] Andre Dietisheim edited comment on JBIDE-19178 at 10/12/15 10:37 AM: --------------------------------------------------------------------- In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {code} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. + Applications + Foo (the application root node; properties view might contain services and routes with actions like, open in browser) + instance-1 (an instance of the application, i.e. the container running the application) + instance-2 + OpenShift + ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: + root + Deployments + Deployment-a + pod-a + instance 1 + container 1 (properties might show the specific build) + pod-b + Services + service-a (properties view might expose related routes) + Builds + Config-a + build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {code} was (Author: adietish): In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {code} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. + Applications + Foo (the application root node; properties view might contain services and routes with actions like, open in browser) + instance-1 (an instance of the application, i.e. the container running the application) + instance-2 + OpenShift + ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: + root + Deployments + Deployment-a + pod-a + instance 1 + container 1 (properties might show the specific build) + pod-b + Services + service-a (properties view might expose related routes) + Builds + Config-a + build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {code} > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:56:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:56:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117427#comment-13117427 ] Andre Dietisheim edited comment on JBIDE-19178 at 10/12/15 10:55 AM: --------------------------------------------------------------------- In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. + Applications + Foo (the application root node; properties view might contain services and routes with actions like, open in browser) + instance-1 (an instance of the application, i.e. the container running the application) + instance-2 + OpenShift + ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: + root + Deployments + Deployment-a + pod-a + instance 1 + container 1 (properties might show the specific build) + pod-b + Services + service-a (properties view might expose related routes) + Builds + Config-a + build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {quote} was (Author: adietish): In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {code} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. + Applications + Foo (the application root node; properties view might contain services and routes with actions like, open in browser) + instance-1 (an instance of the application, i.e. the container running the application) + instance-2 + OpenShift + ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: + root + Deployments + Deployment-a + pod-a + instance 1 + container 1 (properties might show the specific build) + pod-b + Services + service-a (properties view might expose related routes) + Builds + Config-a + build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {code} > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:59:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 10:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117427#comment-13117427 ] Andre Dietisheim edited comment on JBIDE-19178 at 10/12/15 10:58 AM: --------------------------------------------------------------------- In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. * Applications ** Foo (the application root node; properties view might contain services and routes with actions like, open in browser) *** instance-1 (an instance of the application, i.e. the container running the application) *** instance-2 *** OpenShift *** ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: * root ** Deployments *** Deployment-a **** pod-a ***** instance 1 ****** container 1 (properties might show the specific build) ***** pod-b ** Services *** service-a (properties view might expose related routes) ** Builds *** Config-a **** build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {quote} was (Author: adietish): In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. + Applications + Foo (the application root node; properties view might contain services and routes with actions like, open in browser) + instance-1 (an instance of the application, i.e. the container running the application) + instance-2 + OpenShift + ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: + root + Deployments + Deployment-a + pod-a + instance 1 + container 1 (properties might show the specific build) + pod-b + Services + service-a (properties view might expose related routes) + Builds + Config-a + build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {quote} > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:00:02 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 11:00:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117427#comment-13117427 ] Andre Dietisheim edited comment on JBIDE-19178 at 10/12/15 10:59 AM: --------------------------------------------------------------------- In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. * Applications ** Foo (the application root node; properties view might contain services and routes with actions like, open in browser) *** instance-1 (an instance of the application, i.e. the container running the application) *** instance-2 *** OpenShift **** ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: * root ** Deployments *** Deployment-a **** pod-a ***** instance 1 ****** container 1 (properties might show the specific build) ***** pod-b ** Services *** service-a (properties view might expose related routes) ** Builds *** Config-a **** build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {quote} was (Author: adietish): In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. * Applications ** Foo (the application root node; properties view might contain services and routes with actions like, open in browser) *** instance-1 (an instance of the application, i.e. the container running the application) *** instance-2 *** OpenShift *** ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: * root ** Deployments *** Deployment-a **** pod-a ***** instance 1 ****** container 1 (properties might show the specific build) ***** pod-b ** Services *** service-a (properties view might expose related routes) ** Builds *** Config-a **** build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {quote} > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:00:02 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 11:00:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117427#comment-13117427 ] Andre Dietisheim edited comment on JBIDE-19178 at 10/12/15 10:59 AM: --------------------------------------------------------------------- In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. * Applications ** Foo (the application root node; properties view might contain services and routes with actions like, open in browser) *** instance-1 (an instance of the application, i.e. the container running the application) *** instance-2 *** OpenShift **** ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: * root ** Deployments *** Deployment-a **** pod-a ***** instance 1 ****** container 1 (properties might show the specific build) ***** pod-b ** Services *** service-a (properties view might expose related routes) ** Builds *** Config-a **** build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). {quote} was (Author: adietish): In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. * Applications ** Foo (the application root node; properties view might contain services and routes with actions like, open in browser) *** instance-1 (an instance of the application, i.e. the container running the application) *** instance-2 *** OpenShift **** ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: * root ** Deployments *** Deployment-a **** pod-a ***** instance 1 ****** container 1 (properties might show the specific build) ***** pod-b ** Services *** service-a (properties view might expose related routes) ** Builds *** Config-a **** build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). Just some ideas. Feel free to CC other folks or lists. (I just wanted to keep it contained at first and didn't want this to turn into a spam generator.) Rob {quote} > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:02:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 11:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3525: --------------------------------- Steps to Reproduce: 1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ ) 2. Install Arquillian 1.2.0.CR1 from https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/ 3. After install & restart of JBDS, go to Window > Preferences > Install/Update > Available Software Sites and delete or disable the above CR1 site. Leave only the https://devstudio.redhat.com/9.0/stable/updates/ site enabled. (this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1.) 4. Enable EA in Central 5. Make sure https://devstudio.redhat.com/9.0/stable/updates/earlyaccess/ is added and enabled in Window > Preferences > Install/Update > Available Software Sites 6. Check for updates 7. New Arquillian 1.2.0.Final is available, try to update it: {code} An error occurred while collecting items to be installed session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.Final-v20150925-0253-B27 No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.Final-v20150925-0253-B27 No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.Final-v20150925-0253-B27 No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.Final-v20150925-0253-B27 {code} > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:11:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 11:11:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117475#comment-13117475 ] Alexey Kazakov commented on JBDS-3525: -------------------------------------- OK, I reproduced the original problem when you can't update EA stuff from CR1 to GA when EA is enabled. See the "Steps to Reproduce" in this issue. [~nickboldt], [~mickael_istria] so, why the update fails if I have both *https://devstudio.redhat.com/9.0/stable/updates/* and *https://devstudio.redhat.com/9.0/stable/updates/earlyaccess/* (enabled via Central) available in my JBDS? I see the problem with hidden Arquillian in Central if it's already installed but not updated until you check "show installed" too, but it's a separate (and not critical) issue, isn't it? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: arquillian > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:11:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 11:11:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3525: --------------------------------- Component/s: central (was: arquillian) > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:11:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 11:11:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3525: --------------------------------- Priority: Critical (was: Major) > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:16:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 11:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20936) Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20936: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 > Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed. > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20936 > URL: https://issues.jboss.org/browse/JBIDE-20936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:16:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 11:16:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20936) Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20936: -------------------------------------- Assignee: Nick Boldt > Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed. > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20936 > URL: https://issues.jboss.org/browse/JBIDE-20936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:59:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 11:59:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20939) "Bower Update" shortcut does nothing when launched from editor with open bower.json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20939: ----------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-jst/pull/535) > "Bower Update" shortcut does nothing when launched from editor with open bower.json > ----------------------------------------------------------------------------------- > > Key: JBIDE-20939 > URL: https://issues.jboss.org/browse/JBIDE-20939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > Steps to reproduce; > 1) create bower.json via New -> Bower Init wizard > 2) right click on the Editor with newly created bower.json file > 3) Run As -> Bower Update > ERROR: Nothing happens / external process was not launched -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 12:40:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 12 Oct 2015 12:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117520#comment-13117520 ] Nick Boldt commented on JBDS-3537: ---------------------------------- It was moved a year ago. You should be using https://devstudio.redhat.com as that was what we used for JBDS 8. And now 9, and future too. > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 12:48:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 12 Oct 2015 12:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: Denis Golovin created JBIDE-20940: ------------------------------------- Summary: JST test errors on jenkins after recent commits Key: JBIDE-20940 URL: https://issues.jboss.org/browse/JBIDE-20940 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html-source-editing Affects Versions: 4.4.0.Alpha1 Reporter: Denis Golovin {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:4491) at org.eclipse.swt.SWT.error(SWT.java:4406) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) at junit.extensions.TestSetup$1.protect(TestSetup.java:24) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:252) at junit.framework.TestSuite.run(TestSuite.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) 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:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1488) Caused by: java.lang.NullPointerException: null at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) at junit.extensions.TestSetup$1.protect(TestSetup.java:24) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:252) at junit.framework.TestSuite.run(TestSuite.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) 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:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1488) Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 12:50:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 12 Oct 2015 12:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117523#comment-13117523 ] Denis Golovin commented on JBIDE-20940: --------------------------------------- See linked issue JBIDE-20837 . > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 12:52:00 2015 From: issues at jboss.org (master dewa (JIRA)) Date: Mon, 12 Oct 2015 12:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20941) Masterpoker99.com Agen judi Ceme BlackJack, Agen Poker Domino QQ Online In-Reply-To: References: Message-ID: master dewa created JBIDE-20941: ----------------------------------- Summary: Masterpoker99.com Agen judi Ceme BlackJack, Agen Poker Domino QQ Online Key: JBIDE-20941 URL: https://issues.jboss.org/browse/JBIDE-20941 Project: Tools (JBoss Tools) Issue Type: Release Environment: *[Masterpoker99.com Agen judi Ceme BlackJack, Agen Poker Domino QQ Online|http://indoogle.net/masterpoker99-com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online/]* Reporter: master dewa Priority: Minor h1. Masterpoker99.com Agen judi Ceme BlackJack, Agen Poker Domino QQ Online *[Masterpoker99.com Agen judi Ceme BlackJack, Agen Poker Domino QQ Online|http://indoogle.net/masterpoker99-com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online/]* Mungkin bagi para dewa poker media sosial kamu penuh dengan segala macam hal tentang cara main poker online *masterpoker99.com* beberapa hari kedepan. Nah, karena sedang happening, makanya kamu harus simak fakta-fakta yang sudah Agen judi Ceme BlackJack, Agen Poker Domino QQ Online kumpulkan tentang situs masterpoker99.com ini. Sebuah pemain poker99 'pilihan berkaitan dengan mana masterpoker99 dia akan menikmati judi poker online mungkin utama pilihan mempengaruhi pemain 'kenikmatan dari kegiatan ?an nya / agen domino nya. Umumnya, gamer memiliki beberapa kemungkinan tempat untuk memilih dari bandar ceme dan blackjack, mereka: Itu dasarnya memberikan peserta tradisional bukan resiko kas arah ini baru komputer pribadi - diciptakan crawler. ? baru-baru ini tersedia pasar meneliti menyimpulkan bahwa hampir 100 % dari Poker Online Indonesia player yang sakti tentang atau dimiliki penuh berhenti menikmati Poker Online Indonesia mengingat saat ini poker tidak digunakan. h2. Masterpoker99.com Agen judi Ceme BlackJack, Agen Poker Domino QQ Online Alasan Masterpoker99.com Suatu hal yang ketiga untuk mencari dalam situs poker berkaitan dengan jenis permainan poker bahwa website yang menawarkan judi Ceme BlackJack, Agen Poker Domino QQ Online, hal lain yang pemain Poker Online judi ceme calon harus melihat ke dalam hal situs domino qq Online Indonesia sebelum memulai bermain adalah peluang yang baik sebagai orang yang memainkan game ini secara online untuk mencari uang untuk menang. Terakhir, itu selalu baik untuk melakukan latihan bermain yang berkaitan dengan apa yang batas taruhan akan sebelum memilih situs poker yang ingin Anda memanfaatkan. Untuk menghubungi custamer anda b?a telepon yang sedang bertugas, dukungan ?an melihat jika situs poker menawarkan dukungan bebas pulsa dari yurisdiksi bermain atau tidak. Membantu - Anda harus melirik metode bantuan dimana situs masterpoker99.com Masterpoker99.com Agen judi Ceme BlackJack, Agen Poker Domino QQ Online dikelola oleh tim yang anggotanya berusia sekitar 20-an. Diharapkan, konten dari situs masterpoker99 ini akan selalu terbaharui sesuai dengan trend jadwal mantenance. Untuk menentukan empat permainan situsnya, masterpoker99.com melakukan analisis data dengan menentukan indikator-indikator tertentu. Tulisan ini saya kaitkan dari beberapa sumber yaitu: 1. http://indoogle.net/masterpoker99-com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online/ 2. https://wikis.nyu.edu/display/~vas281/2015/09/24/Masterpoker99.com+Agen+Judi+Ceme+BlackJack,+Agen+Poker+Domino+QQ+Online 3. http://eco.netvibes.com/themes/589356/masterpoker99-com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online 4. http://softwarelivre.org/node/blog/masterpoker99.com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online 5. https://jira.atlassian.com/browse/TST-72535 6. http://weheartit.com/masterpoker99 7. http://tinychat.com/masterpoker99 8. http://www.gamedesire.com/player/masterpoker99com/blog/2534237 9. https://datafox.co/masterpoker99-com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online 10. http://www.participa.br/content/blog/masterpoker99.com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online 11. https://github.com/indoogle/Masterpoker99.com-Agen-Judi-Ceme-BlackJack-Agen-Poker-Domino-QQ-Online 12. https://www.crunchbase.com/organization/masterpoker99-com-agen-judi-ceme-blackjack-agen-poker-domino-qq-online 13. http://www.mapmyride.com/id/jakarta-jakarta-raya/masterpoker99-com-agen-judi-ceme-blackja-group-678101 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 12:54:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 12 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117524#comment-13117524 ] Denis Golovin commented on JBIDE-20940: --------------------------------------- {code} if(selectedViewer instanceof AbstractPropertySetViewer) { Display.getDefault().asyncExec(new Runnable() { public void run() { ((AbstractPropertySetViewer)selectedViewer).updateUI(); } }); } {code} This is the suspect :) since it is unknown when updateUI() is going to be called there should be additional check for selectedViewer inside run method. > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 12:54:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 12 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin reassigned JBIDE-20940: ------------------------------------- Assignee: Viacheslav Kabanovich > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 12:54:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 12 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20940: ---------------------------------- Priority: Critical (was: Major) > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Critical > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 13:10:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Mon, 12 Oct 2015 13:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20741) JVM Navigator "Link with Editor" toggle button force current selection to be current and visible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker updated JBIDE-20741: -------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.x) > JVM Navigator "Link with Editor" toggle button force current selection to be current and visible > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-20741 > URL: https://issues.jboss.org/browse/JBIDE-20741 > 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.Final > > Attachments: viewer-linking.mp4 > > > Watch attached [^viewer-linking.mp4] to see actual behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 13:10:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Mon, 12 Oct 2015 13:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20741) JVM Navigator "Link with Editor" toggle button force current selection to be current and visible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117528#comment-13117528 ] Rob Stryker commented on JBIDE-20741: ------------------------------------- Thanks for the video, clarifies the issue perfectly. > JVM Navigator "Link with Editor" toggle button force current selection to be current and visible > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-20741 > URL: https://issues.jboss.org/browse/JBIDE-20741 > 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.Final > > Attachments: viewer-linking.mp4 > > > Watch attached [^viewer-linking.mp4] to see actual behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 13:35:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 13:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20942) HTML5 Tabbed Properties View Problems In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20942: -------------------------------------- Summary: HTML5 Tabbed Properties View Problems Key: JBIDE-20942 URL: https://issues.jboss.org/browse/JBIDE-20942 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html-source-editing Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Fix For: 4.3.1.Final, 4.4.0.Alpha1 1. Tab "All" by default has collapsed column "Name": !HTML5_Properties_View.png! 2. Tab "jQuery" does not take into account size of vertical scrollbar: !HTML5_Properties_View2.png! Test case: 1. Install JBDS 2. Import HTML5 Project "jboss-as-kitchensink-html5-mobile" 3. Open index.html in Visual Page Editor 4. Make View "Properties" active 5. Select different tags in the editor and watch theyr properties in Properties View -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 13:35:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 13:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20942) HTML5 Tabbed Properties View Problems In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20942: ----------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > HTML5 Tabbed Properties View Problems > ------------------------------------- > > Key: JBIDE-20942 > URL: https://issues.jboss.org/browse/JBIDE-20942 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final > > Attachments: HTML5_Properties_View.png, HTML5_Properties_View2.png > > > 1. Tab "All" by default has collapsed column "Name": > !HTML5_Properties_View.png! > 2. Tab "jQuery" does not take into account size of vertical scrollbar: > !HTML5_Properties_View2.png! > Test case: > 1. Install JBDS > 2. Import HTML5 Project "jboss-as-kitchensink-html5-mobile" > 3. Open index.html in Visual Page Editor > 4. Make View "Properties" active > 5. Select different tags in the editor and watch theyr properties in Properties View -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 13:35:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 13:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20942) HTML5 Tabbed Properties View Problems In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20942. ------------------------------------ Resolution: Done > HTML5 Tabbed Properties View Problems > ------------------------------------- > > Key: JBIDE-20942 > URL: https://issues.jboss.org/browse/JBIDE-20942 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Final > > Attachments: HTML5_Properties_View.png, HTML5_Properties_View2.png > > > 1. Tab "All" by default has collapsed column "Name": > !HTML5_Properties_View.png! > 2. Tab "jQuery" does not take into account size of vertical scrollbar: > !HTML5_Properties_View2.png! > Test case: > 1. Install JBDS > 2. Import HTML5 Project "jboss-as-kitchensink-html5-mobile" > 3. Open index.html in Visual Page Editor > 4. Make View "Properties" active > 5. Select different tags in the editor and watch theyr properties in Properties View -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 13:36:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 13:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20837) HTML5 Tabbed Properties View Problems In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20837: ----------------------------------- Fix Version/s: (was: 4.3.1.Final) > HTML5 Tabbed Properties View Problems > ------------------------------------- > > Key: JBIDE-20837 > URL: https://issues.jboss.org/browse/JBIDE-20837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > Attachments: HTML5_Properties_View.png, HTML5_Properties_View2.png > > > 1. Tab "All" by default has collapsed column "Name": > !HTML5_Properties_View.png! > 2. Tab "jQuery" does not take into account size of vertical scrollbar: > !HTML5_Properties_View2.png! > Test case: > 1. Install JBDS > 2. Import HTML5 Project "jboss-as-kitchensink-html5-mobile" > 3. Open index.html in Visual Page Editor > 4. Make View "Properties" active > 5. Select different tags in the editor and watch theyr properties in Properties View -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 13:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 12 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20940: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 14:22:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 14:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-501) stable URLs used for Integration Stack installs/updates via Central should not contain a version number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-501. ------------------------------ Resolution: Done All versioned IS-related URLs have been corrected. > stable URLs used for Integration Stack installs/updates via Central should not contain a version number > ------------------------------------------------------------------------------------------------------- > > Key: JBTIS-501 > URL: https://issues.jboss.org/browse/JBTIS-501 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.2.3.Final , 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Stable URLs used for Integration Stack installs/updates via Central should not contain a version number, so that users only see ONE URL, which is updated to contain new, fresh content. > This allows new users to see the latest updates, existing users to see newer updates (Help > Check for updates), and existing users to seek new updates in Central, too. > So... > {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L82} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/{code} > Needs to change to > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > And http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ needs to be a composite of http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 14:39:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 14:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-517: -------------------------------- Assignee: Paul Leacu > Update web pages for JBDS-IS 9.x > -------------------------------- > > Key: JBTIS-517 > URL: https://issues.jboss.org/browse/JBTIS-517 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Attachments: jbdsis-900alpha2-webpage.png, jbdsis-900alpha2ea-webpage.png > > > Update web pages for JBDS-IS 9.x at > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ > See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 15:35:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 15:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 3:34 PM: -------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker labels or openshift annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" (via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 15:42:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 15:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-519) Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-519: -------------------------------- Assignee: Gomathi Anandan > Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP > ------------------------------------------- > > Key: JBTIS-519 > URL: https://issues.jboss.org/browse/JBTIS-519 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Gomathi Anandan > > Please upload JBDS-IS 9.0.0.Alpha2 zip files to CSP -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 15:43:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 15:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-519) Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117553#comment-13117553 ] Paul Leacu commented on JBTIS-519: ---------------------------------- Hey G - The JBDSIS 9.0.0.Alpha2 zip files are: * https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip (MD5) * https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip (MD5) Thkx! > Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP > ------------------------------------------- > > Key: JBTIS-519 > URL: https://issues.jboss.org/browse/JBTIS-519 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Gomathi Anandan > > Please upload JBDS-IS 9.0.0.Alpha2 zip files to CSP -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 16:04:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 12 Oct 2015 16:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-519) Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117556#comment-13117556 ] Paul Leacu commented on JBTIS-519: ---------------------------------- Software Description Red Hat JBoss Developer Studio Integration Stack 9.0.0.Alpha2 Update Site Zips Detailed Description These release zips have been certified for JBoss Developer Studio 9.0.0.GA. Manual Instructions 1. Start jbdevstudio 2. Select the Software/Update tab in the JBoss Central view. Check the "Enable Early Access" check box to see the integration stack early access components. To use either of these zips for offline update (or if blocked by firewall or proxy): - Download the zip, but DO NOT unpack it - Launch JBDS. - Select Help > Install new software - Click Add and browse for the zip - Select the feature(s) you wish to install and accept the licenses - Restart when prompted > Upload JBDS-IS 9.0.0.Alpha2 zip file to CSP > ------------------------------------------- > > Key: JBTIS-519 > URL: https://issues.jboss.org/browse/JBTIS-519 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Gomathi Anandan > > Please upload JBDS-IS 9.0.0.Alpha2 zip files to CSP -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 17:04:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 17:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 5:03 PM: -------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker labels or openshift annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 17:18:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 17:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 5:17 PM: -------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 17:20:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 17:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 5:19 PM: -------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} [~maxandersen]: My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 17:23:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 17:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 5:22 PM: -------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} [~maxandersen]: My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) {quote} [~maxandersen] "dev mode" Which enables debug and allows admin operations. {quote} * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} [~maxandersen]: My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 18:27:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 18:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 6:26 PM: -------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} [~maxandersen]: My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) {quote} [~maxandersen] "dev mode" Which enables debug and allows admin operations. {quote} * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} [~maxandersen]: My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) {quote} [~maxandersen] "dev mode" Which enables debug and allows admin operations. {quote} * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 18:27:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 12 Oct 2015 18:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117420#comment-13117420 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/12/15 6:26 PM: -------------------------------------------------------------------- in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} [~maxandersen]: My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) {quote} [~maxandersen] "dev mode" Which enables debug and allows admin operations. {quote} * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} was (Author: adietish): in a mail by [~rcernich] on the 10th of August "JBoss OpenShift Dev/Debug Requirements" {quote} I'm guessing the ideal flow is for users to simply right-click a project and "Run/Debug As => OpenShift Application." The following details would then need to be specified (or inferred from the project): * OpenShift instance * OpenShift project * "Application" name (default to project name) * Server type (e.g. EAP, JWS, etc.; default based on project type, e.g. war=eap) * Base image (e.g. eap64-openshift, webserver30-tomcat7-openshift, etc.; default based on app-type) * Deployment directory (discover from image) {quote} [~maxandersen]: My hope was that in openshift context we could query this through openshift api - but yeah, if that is not possible then we would need to have the docker image above and have the docker tooling configured to access the same image/registries as openshift has. For now we should default to "/deployments", but yes optimally get it from the image but always as fallback have a way for user to explicitly specify it. So basically the read-priority for this is: 1) user explicitly specified value 2) get from image when possible 3) if not possible, assume /deployments (or whatever default it was the cloud images ended up using) {quote} * Debug port (discover from image) (via DEBUG docker env var) Given that, we would create an application on OS containing a dc, a service and a route. The dc comes up, the deployment is sync'd. You'd have to decide whether you'd want to remove the objects when the application is stopped. The next use case might be to attach to an already running instance, which should be a lot less complicated. The only detail I see missing here is possibly having to configure debug on the pod (so the debug port on the server becomes available). Extracting some requirements based on the above, I think we end up needing the following: * label specifying deployment directory (already exists: org.jboss.deployments-dir) * label specifying debug port * flag enabling debug (to expose the debug port on the server/jvm) {quote} [~maxandersen] "dev mode" Which enables debug and allows admin operations. {quote} * flag enabling "hot deploy" {quote} via possibility to mount /deployments -> upstream k8s issue where containers can be modified, committed and pushed to registry) {quote} * label specifying server type (currently env variables: JBOSS_PRODUCT, JBOSS_EAP_VERSION) {quote} There's no consensus yet whether docker or k8s labels or k8s annotation shall be used, while it seems annotations are what is preferred for tools. Then uncertain is whether docker labels are propagated (while they apparently should) to openshift annotations. {code:title=https://github.com/openshift/origin/blob/master/examples/image-streams/image-streams-centos7.json#L21-L27} "annotations": { "description": "Build and run Ruby 2.0 applications", "iconClass": "icon-ruby", "tags": "builder,ruby", "supports": "ruby:2.0,ruby", "version": "2.0", "sampleRepo": "https://github.com/openshift/ruby-ex.git" {code} {quote} Complications: * Networking - How do you connect to the debug port? Is that a service? Do we go through a route using SNI? * Creating the image - Do we create a dummy image, then rsync the contents? Do we create an image locally and push it to the OS registry? * Permissions - Are there any special permissions that users would need to have to enable debugging, opening ports, etc.? * Committing the image - How do we want to handle changes that a user might make to an image: drop them, commit them? More fun stuff: * Could we enable existing "servers view" content off of pod nodes (e.g. EAP view, but rooted at a pod instead of server)? * What about source types beyond git (e.g. curl, blob, rsync, empty)? {quote} > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 04:52:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Tue, 13 Oct 2015 04:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20943) WP engines are being downloaded but not recognized in UI In-Reply-To: References: Message-ID: Pavol Srna created JBIDE-20943: ---------------------------------- Summary: WP engines are being downloaded but not recognized in UI Key: JBIDE-20943 URL: https://issues.jboss.org/browse/JBIDE-20943 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid, upstream Affects Versions: 4.3.0.Final Reporter: Pavol Srna Fix For: 4.3.x https://bugs.eclipse.org/bugs/show_bug.cgi?id=479630 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 04:58:00 2015 From: issues at jboss.org (Pavol Srna (JIRA)) Date: Tue, 13 Oct 2015 04:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20944) Eclipse THYM version and THYM plugins versions should be in sync In-Reply-To: References: Message-ID: Pavol Srna created JBIDE-20944: ---------------------------------- Summary: Eclipse THYM version and THYM plugins versions should be in sync Key: JBIDE-20944 URL: https://issues.jboss.org/browse/JBIDE-20944 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid, upstream Affects Versions: 4.3.0.Final Reporter: Pavol Srna Fix For: 4.3.x https://bugs.eclipse.org/bugs/show_bug.cgi?id=479631 Eclipse THYM version and THYM plugins version are not in sync. It is incredibly hard to verify and target bugs for releases when the versions do not match. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 06:03:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Tue, 13 Oct 2015 06:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20698) tools.jboss.org/features: Add WildFly 9, 10 and EAP 7 to the list of supported servers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117651#comment-13117651 ] Martin Malina commented on JBIDE-20698: --------------------------------------- I created a PR to add the note that Fred is asking for: https://github.com/jbosstools/jbosstools-website/pull/520 > tools.jboss.org/features: Add WildFly 9,10 and EAP 7 to the list of supported servers > ------------------------------------------------------------------------------------- > > Key: JBIDE-20698 > URL: https://issues.jboss.org/browse/JBIDE-20698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Fix For: 4.3.0.Final > > > We should update http://tools.jboss.org/features/server.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 10:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 10:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20943) WP engines are being downloaded but not recognized in UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20943: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.x) > WP engines are being downloaded but not recognized in UI > -------------------------------------------------------- > > Key: JBIDE-20943 > URL: https://issues.jboss.org/browse/JBIDE-20943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.Final > Reporter: Pavol Srna > Fix For: 4.3.1.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=479630 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 10:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 10:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20943) WP engines are being downloaded but not recognized in UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20943: -------------------------------------- Assignee: Gorkem Ercan > WP engines are being downloaded but not recognized in UI > -------------------------------------------------------- > > Key: JBIDE-20943 > URL: https://issues.jboss.org/browse/JBIDE-20943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.Final > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.1.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=479630 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 10:26:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 10:26:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20944) Eclipse THYM version and THYM plugins versions should be in sync In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20944: -------------------------------------- Assignee: Gorkem Ercan > Eclipse THYM version and THYM plugins versions should be in sync > ---------------------------------------------------------------- > > Key: JBIDE-20944 > URL: https://issues.jboss.org/browse/JBIDE-20944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.Final > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=479631 > Eclipse THYM version and THYM plugins version are not in sync. It is incredibly hard to verify and target bugs for releases when the versions do not match. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 11:17:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 13 Oct 2015 11:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117809#comment-13117809 ] Nick Boldt commented on JBIDE-20918: ------------------------------------ PR https://github.com/jbosstools/jbosstools-browsersim/pull/78/ was applied but https://github.com/jbosstools/jbosstools-aerogear/pull/149 has not been so builds are stil failing because of the unchanged code below which still requires old Jetty 9.2 instead of what's in the TP, 9.3. Can you apply your PR ASAP? {code} ** [1] ./jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/META-INF/MANIFEST.MF ** 29- org.eclipse.jetty.io;bundle-version="[9.2.13,9.2.14)", 30- org.eclipse.jetty.security;bundle-version="[9.2.13,9.2.14)", 31: org.eclipse.jetty.server;bundle-version="[9.2.13,9.2.14)", 32- org.eclipse.jetty.servlet;bundle-version="[9.2.13,9.2.14)", 33- org.eclipse.jetty.servlets;bundle-version="[9.2.13,9.2.14)", ** [2] ./jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim/META-INF/MANIFEST.MF ** 11- org.jboss.tools.browsersim.javafx.mock;bundle-version="3.7.0";resolution:=optional, 12- org.eclipse.swt, 13: org.eclipse.jetty.server;bundle-version="[9.2.13,9.2.14)", 14- org.eclipse.jetty.util;bundle-version="[9.2.13,9.2.14)", 15- org.apache.aries.spifly.dynamic.bundle;bundle-version="1.0.2" ** [3] ./jbosstools-aerogear/cordovasim/tests/org.jboss.tools.cordovasim.eclipse.test/META-INF/MANIFEST.MF ** 13- org.eclipse.core.resources, 14- org.jboss.tools.locus.mockito, 15: org.eclipse.jetty.server;bundle-version="[9.2.13,9.2.14)", 16- org.eclipse.jetty.util;bundle-version="[9.2.13,9.2.14)" 17-Bundle-RequiredExecutionEnvironment: JavaSE-1.7 {code} > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 11:21:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 13 Oct 2015 11:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117813#comment-13117813 ] Nick Boldt commented on JBIDE-20918: ------------------------------------ Build breakage looks like this: {code} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 10.0.0.qualifier [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.0.Alpha1-v20151006-0724-B246 requires 'bundle org.eclipse.jetty.server [9.2.13,9.2.14)' but it could not be found [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.0.0.qualifier depends on: org.jboss.tools.browsersim.feature.feature.group 0.0.0 [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.feature.feature.group 3.8.0.Alpha1-v20151006-0724-B246 depends on: org.jboss.tools.browsersim.ui [3.8.0.Alpha1-v20151006-0724-B246] {code} > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 11:26:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 13 Oct 2015 11:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117816#comment-13117816 ] Nick Boldt commented on JBIDE-20918: ------------------------------------ Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-aerogear_master/ >=531 > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 11:33:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 13 Oct 2015 11:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117820#comment-13117820 ] Nick Boldt commented on JBIDE-20918: ------------------------------------ Built. http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aerogear_master/latest/all/repo/ (Latest Build: 1.3.0-SNAPSHOT (Alpha1-v20151013-1527-B531)) Now compositing and verifying everything builds downstream: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/ >=10940 http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_master/ >=4030 > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 12:56:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 13 Oct 2015 12:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20937) Create resource(s) from json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117841#comment-13117841 ] Fred Bricon commented on JBIDE-20937: ------------------------------------- [~jcantrill], [~adietish] : is this something the rest client supports today? > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Critical > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 13:24:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 13 Oct 2015 13:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117849#comment-13117849 ] Fred Bricon commented on JBIDE-20935: ------------------------------------- [~jrichter1]: did you try on other platforms / windows 7/8? [~snjeza]: do you happen to have some windows installed to check that one? > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Attachments: central.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 13:27:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 13 Oct 2015 13:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20937) Create resource(s) from json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117852#comment-13117852 ] Jeff Cantrill commented on JBIDE-20937: --------------------------------------- The rest client does support creating resources from JSON. This is what we do for deploy image. > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Critical > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 13:31:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Tue, 13 Oct 2015 13:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin reassigned JBDS-3535: ----------------------------------- Assignee: Daniel Azarov (was: Denis Golovin) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.x, 9.x > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 13:37:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Tue, 13 Oct 2015 13:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20926) Visual Preview tests fail on windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117857#comment-13117857 ] Konstantin Marmalyukov commented on JBIDE-20926: ------------------------------------------------ I believe it is slave problem. Locally this test passes fine. > Visual Preview tests fail on windows > ------------------------------------ > > Key: JBIDE-20926 > URL: https://issues.jboss.org/browse/JBIDE-20926 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha1 > Environment: Windows IE11 x86_64 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > {code}externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.671 sec <<< ERROR! > java.lang.Exception: Refresh does not happens > at org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest.externalUrlReloadTest(PreviewReloadTest.java:72) > externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.681 sec <<< FAILURE! > java.lang.AssertionError: Refresh does not happens > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.tools.vpe.preview.editor.test.editor.VpvTest.failOnException(VpvTest.java:68) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 13:38:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Tue, 13 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117858#comment-13117858 ] Snjezana Peco commented on JBIDE-20935: --------------------------------------- The issue can be reproduced on Windows 7. > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Attachments: central.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 13:42:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 13 Oct 2015 13:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20937) Create resource(s) from json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117861#comment-13117861 ] Fred Bricon commented on JBIDE-20937: ------------------------------------- Potential UI : !https://issues.jboss.org/secure/attachment/12393869/New%20Resource%20Wizard%20Mockup.png! > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Critical > Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 14:26:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 13 Oct 2015 14:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20937) Create resource(s) from json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117872#comment-13117872 ] Jeff Cantrill commented on JBIDE-20937: --------------------------------------- Seems reasonable if the 'create from text' was maybe a YAML editor that is offered like doing 'oc edit'. My only concern with the editor is that a user needs know the API, but this probably isnt any different from needing to it to create the json. Might it also be useful for you to be able to save the text back to a file? > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Critical > Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 14:38:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Tue, 13 Oct 2015 14:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin closed JBIDE-20940. --------------------------------- No more errors on jenkins > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 16:15:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 13 Oct 2015 16:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20918) Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20918. ------------------------------ Builds are blue. Closing. > Browsersim and Cordovasim are broken since jetty v 9.3.2 was added to TP > ------------------------------------------------------------------------ > > Key: JBIDE-20918 > URL: https://issues.jboss.org/browse/JBIDE-20918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > In 4.60.0.Alpha1 we have jetty 9.3.2. Since in this jetty version bug with restriction of version of jetty dependencies we have to follow eclipse with jetty versions. > The reason why Browsersim and Cordovasim cannot be launched: we have two versions of Jetty bundles in TP. Since we require lower versions we have dependency chains. To fix it, we need to update Jetty to 9.3.2 > See JBIDE-20670 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 16:33:00 2015 From: issues at jboss.org (Giovanni Tomasicchio (JIRA)) Date: Tue, 13 Oct 2015 16:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117914#comment-13117914 ] Giovanni Tomasicchio commented on JBIDE-20071: ---------------------------------------------- There is an issue with exploded jars in WEB-INF/lib and JBoss EAP 6.4. JBoss return a 404 error for resource files placed in META-INF/resources folder of an exploded jar. This error does not occur if the jar is compressed. For reference see Servlet 3.0 specs, chapter 10.5. Tested environment: Eclipse Mars 1 - JBoss Tools 4.3.0.Final - JBoss EAP 6.4.3 > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 16:36:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 13 Oct 2015 16:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117915#comment-13117915 ] Fred Bricon commented on JBIDE-20071: ------------------------------------- [~giannitom]: could you please open a new ticket and attach a sample project demonstrating the error? > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 16:42:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Tue, 13 Oct 2015 16:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117919#comment-13117919 ] Rob Stryker commented on JBIDE-20071: ------------------------------------- [~giannitom] I've read the spec pages for reference: _The Web application class loader must load classes from the WEB-INF/classes directory first, and then from library JARs in the WEB-INF/lib directory. Also, except for the case where static resources are packaged in JAR files, any requests from the client to access the resources in WEB-INF/ directory must be returned with a SC_NOT_FOUND (404) response. _ This seems to be not a bug, but rather according to spec. Users who use exploded deployment should not be placing their resources in the WEB-INF folder or it will be met with a 404. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 17:14:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 13 Oct 2015 17:14:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3245: ----------------------------- > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 17:14:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Tue, 13 Oct 2015 17:14:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3245: -------------------------------- > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 17:14:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 17:14:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3245: --------------------------------- Target Release: 10.0.0.GA (was: 9.0.0.GA) > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 17:24:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 13 Oct 2015 17:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117932#comment-13117932 ] Fred Bricon commented on JBDS-3245: ----------------------------------- Instead of punting that Epic from release to release, couldn't we just have "Improve Eclipse Neon Platform" for JBDS 10.0.0.GA and resolve it once released. And create a new Epic for, say, "Improve Eclipse Optimus Prime Platform" targeted at JBDS 11? > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 17:32:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Tue, 13 Oct 2015 17:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20741) JVM Navigator "Link with Editor" toggle button force current selection to be current and visible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117935#comment-13117935 ] Rob Stryker commented on JBIDE-20741: ------------------------------------- Seems its even worse. If you select something in attributes or operations viewer inside editor, it gets stuck in an endless loop, updating the jmx view, then updating the editor, repeat. Woohoo. > JVM Navigator "Link with Editor" toggle button force current selection to be current and visible > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-20741 > URL: https://issues.jboss.org/browse/JBIDE-20741 > 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.Final > > Attachments: viewer-linking.mp4 > > > Watch attached [^viewer-linking.mp4] to see actual behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 17:42:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 17:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117936#comment-13117936 ] Alexey Kazakov commented on JBDS-3245: -------------------------------------- Fred, this is the question I have been raising, but it's still not clear to me what is the best approach. Should we have version specific epics? In this particular case with Improve Eclipse Platform epic I would use separate epics for each major Eclipse release otherwise this epic will never be resolved. But btw we can't resolve "Improve Eclipse Neon Platform" epic as soon as JBDS 10.0.0 is out because we probably will want to release JBDS 10.0.1 based on Neon.1 or 2 ;-) > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 18:01:01 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Tue, 13 Oct 2015 18:01:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20741) JVM Navigator "Link with Editor" toggle button force current selection to be current and visible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker updated JBIDE-20741: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > JVM Navigator "Link with Editor" toggle button force current selection to be current and visible > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-20741 > URL: https://issues.jboss.org/browse/JBIDE-20741 > 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.Final, 4.4.0.Alpha1 > > Attachments: viewer-linking.mp4 > > > Watch attached [^viewer-linking.mp4] to see actual behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 18:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 18:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117943#comment-13117943 ] Alexey Kazakov commented on JBDS-3525: -------------------------------------- And BTW. EA update site is added only when I started to install anything from central with EA enabled. Shouldn't we add the EA update site as soon as EA is enabled in Central and not wait for an actual installation attempt? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 20:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 20:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117949#comment-13117949 ] Alexey Kazakov commented on JBDS-3525: -------------------------------------- It actually sometimes works sometimes doesn't! Maybe it's actually the same problem we are experiencing with download site: JBDS-3537 JBDS-3538 https://marketplace.eclipse.org/content/jboss-tools ? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 20:53:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 13 Oct 2015 20:53:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117949#comment-13117949 ] Alexey Kazakov edited comment on JBDS-3525 at 10/13/15 8:52 PM: ---------------------------------------------------------------- It actually sometimes updates sometimes doesn't! Maybe it's actually the same problem we are experiencing with download site: JBDS-3537 JBDS-3538 https://marketplace.eclipse.org/content/jboss-tools ? was (Author: akazakov): It actually sometimes works sometimes doesn't! Maybe it's actually the same problem we are experiencing with download site: JBDS-3537 JBDS-3538 https://marketplace.eclipse.org/content/jboss-tools ? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 21:14:00 2015 From: issues at jboss.org (Daniel Azarov (JIRA)) Date: Tue, 13 Oct 2015 21:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117958#comment-13117958 ] Daniel Azarov commented on JBDS-3535: ------------------------------------- PR - https://github.com/jbdevstudio/jbdevstudio-product/pull/345 > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.x, 9.x > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 00:13:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 14 Oct 2015 00:13:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117962#comment-13117962 ] Nick Boldt commented on JBDS-3245: ---------------------------------- I like version specific ones when they're specific to a version of Eclipse or JBDS. For example: JBDS-3299 (JBDS 9 / Mars) JBDS-3536 (JBDS 10 / Neon) Conversely, ongoing improvements live in Epics which can be punted from release to release: JBIDE-19730 $0.02, Nick > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 00:16:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 14 Oct 2015 00:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20930) Marketplace entry for JBT says it is for "Eclipse Luna" for every version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20930: ------------------------------- Fix Version/s: 4.3.0.Final (was: 4.3.1.Final) > Marketplace entry for JBT says it is for "Eclipse Luna" for every version > ------------------------------------------------------------------------- > > Key: JBIDE-20930 > URL: https://issues.jboss.org/browse/JBIDE-20930 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > JBT marketplace entry says this: "JBoss Tools is an umbrella project for a set of Eclipse Luna plugins." And since there is only one entry for all available versions, it says that every time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 00:16:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 14 Oct 2015 00:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20930) Marketplace entry for JBT says it is for "Eclipse Luna" for every version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBIDE-20930. -------------------------------- Resolution: Done The word "Luna" has been removed from the description. > Marketplace entry for JBT says it is for "Eclipse Luna" for every version > ------------------------------------------------------------------------- > > Key: JBIDE-20930 > URL: https://issues.jboss.org/browse/JBIDE-20930 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > JBT marketplace entry says this: "JBoss Tools is an umbrella project for a set of Eclipse Luna plugins." And since there is only one entry for all available versions, it says that every time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 00:18:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 14 Oct 2015 00:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117964#comment-13117964 ] Nick Boldt commented on JBDS-3538: ---------------------------------- Problems also being reported attempting to install JBoss Tools: {code} When i want to install jboss from marketplace on a new clean Mars.1 (downloaded eclipse-jee-mars-1-win32-x86_64.zip from eclipse) the download ends with the following message: An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Error closing the output stream for osgi.bundle,ternjs,1.0.0.201508302102 on repository file:/C:/entw/Mars.1/. Error unzipping c:\TEMP\ternjs_1.0.0.2015083021026612838725989430243.jar: Unexpected end of ZLIB input stream - See more at: https://marketplace.eclipse.org/content/jboss-tools#sthash.dV0a9taA.dpuf The file "ternjs_1.0.0.201508302102.jar" from the url [http] "download.jboss.org/jbosstools/static/mars/stable/updates/core/4.3.0.Final/plugins/" seems to be broken. We tried to download this jar file over several connections and everytime we got an broken 2.5 MB jar file instead of the 12 MB jar file it should be. - See more at: https://marketplace.eclipse.org/content/jboss-tools#sthash.dV0a9taA.dpuf {code} -- https://marketplace.eclipse.org/content/jboss-tools > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 01:33:00 2015 From: issues at jboss.org (Giovanni Tomasicchio (JIRA)) Date: Wed, 14 Oct 2015 01:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117970#comment-13117970 ] Giovanni Tomasicchio commented on JBIDE-20071: ---------------------------------------------- [~rob.stryker]i'm refering to this part of specs: ??For example, for a Web application with the context path /catalog in a Web container, the index.html file at the base of the Web application hierarchy or +in a JAR file inside WEB-INF/lib that includes the index.html under META-INF/resources directory+ can be served to satisfy a request from /catalog/index.html.?? > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 02:52:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 02:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117980#comment-13117980 ] Denis Golovin commented on JBDS-3525: ------------------------------------- This is IMO download sever connection problem. If eclipse install dialog let you continue, it means all metadata was downloaded and selected features were verified to be valid to proceed with installation. Then required binary artifacts were not available for some reason. It feels like some exceptions were ignored, so we cannot see what was the real reason. BTW I would run JBDS from console to see standard output, it might have some exceptions printed out. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 03:04:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 03:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117988#comment-13117988 ] Denis Golovin commented on JBIDE-20927: --------------------------------------- Right, but test is required to verify "that these validators are excluded if they are available". You cannot verify it if they are not available during the test. > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 03:37:01 2015 From: issues at jboss.org (Vladimir Vasilev (JIRA)) Date: Wed, 14 Oct 2015 03:37:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117997#comment-13117997 ] Vladimir Vasilev commented on JBDS-3538: ---------------------------------------- Do we have timestamp on this issue? > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 03:58:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 03:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118003#comment-13118003 ] Max Rydahl Andersen commented on JBDS-3245: ------------------------------------------- +1 for stream specific eclipse platform epic. > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 04:09:03 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 04:09:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118005#comment-13118005 ] Max Rydahl Andersen commented on JBDS-3538: ------------------------------------------- [~vladimir_v] not beyound the time of his comments. October 8, 2015 - 05:12 October 9, 2015 - 06:05 I assume the timezone is EST for this. Ive asked on the mp entry that he gives more info but lets not wait for that to check if we can, > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 04:19:00 2015 From: issues at jboss.org (Vladimir Vasilev (JIRA)) Date: Wed, 14 Oct 2015 04:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118009#comment-13118009 ] Vladimir Vasilev commented on JBDS-3538: ---------------------------------------- [~maxandersen], I'm afraid Akamai keep logs for the last 24-48 hours. We need something more recent. > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 04:24:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 14 Oct 2015 04:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20937) Create resource(s) from json In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20937: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 04:31:03 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 14 Oct 2015 04:31:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118014#comment-13118014 ] Andre Dietisheim commented on JBIDE-20764: ------------------------------------------ [~maxandersen] any thoughts on the 1st try for a mock? > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Final > > Attachments: server adapter wizard.bmml, server adapter wizard.png > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 04:31:03 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 14 Oct 2015 04:31:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118013#comment-13118013 ] Andre Dietisheim commented on JBIDE-19178: ------------------------------------------ [~maxandersen] any thoughts on the 1st try for a mock? > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 04:33:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 04:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118015#comment-13118015 ] Mickael Istria commented on JBDS-3537: -------------------------------------- [~asmigala] There is some mirroring set up under the "static" folder, which is delegated to Akamai. Akamai takes care of setting up mirrors where necessary and so on. It's mostly a blackbox for us. Can you still reproduce the issue? I tried multiple wget on the same URL as the one in the bug description, and got 8 successful downloads out of 8. > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 04:37:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 04:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBTIS-520: ----------------------------------------- Summary: developer urls in our stable stream Key: JBTIS-520 URL: https://issues.jboss.org/browse/JBTIS-520 Project: JBoss Tools Integration Stack Issue Type: Bug Components: releng Reporter: Max Rydahl Andersen Priority: Blocker JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 earlyaccess is correct, but not the main IS site. according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 05:51:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 05:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118057#comment-13118057 ] Max Rydahl Andersen commented on JBIDE-19178: --------------------------------------------- I can't really follow why workspace projects are at same level as the "Y openshift project" ....what are the openshift.redhat.com and eap6 server ? on which of possibly many containers is the debug port 4000 for ? What is the /deployments node ? [~rcernich]'s suggestions about using application=foo + filters made a lot of sense to me but I don't quite get how those concepts maps into your proposal. can you explain a bit what those various nodes mean and how they are found ? > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 05:51:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 05:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118059#comment-13118059 ] Max Rydahl Andersen commented on JBIDE-19178: --------------------------------------------- [~jcantrill] [~hardy.ferentschik] see above. feedback welcome. > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:06:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 06:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118067#comment-13118067 ] Mickael Istria commented on JBDS-3525: -------------------------------------- I tried a variant of the steps to reproduce provided by [~akazakov] and managed to get Arquillian updated. However, instead of using "Check for updates", I did click "Show installed", selected "JBoss Arquillian" and clicked "Install/Update". Everything worked as expected, so it shows that the sites are not to blame. Then I re-started from scratch and run exactly the steps to reproduce. And everything worked as expected too. I'm enclined to believe that this is a symptom of the download problems we're facing. The download of p2 metadata may have failed and upgrade too as a consequence. About the meaning of "Enable early-access", this should be treated in a separate Jira. Anyway, I feel it's interesting to explain the conceptual issues here: Early-Access meaning has been evolving over its adoption. Currently, in UI, it only sets a preference allowing to "show early access content" in catalog. It was actually called like that initially, but "enable Early-Access" was preferred. The underlying early-access site used by early-access connectors is only added by p2 as an available site when installing some early-access content. So just ticking "enable early-access" doesn't make early-access content available when udpating. It seems now that early-access isn't really a certificationId for a discovery entry nor a preference, but just a p2 repository with a specific URL; that enabling early-access is enabling this site as visible, and that an early-access connector is a connector that references this early-access site. However, it's not what's implemented in 4.3.0 and 9.0.0. Actually, it's even possible that the definition proposed above is already outdated by the ability of other content providers (JBT-IS, JBDS-IS) to use an alternative site which is early-access. In such case, is the JBT-IS EA site expected to be visible when doing "Check for updates"...? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:17:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 06:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118072#comment-13118072 ] Max Rydahl Andersen commented on JBDS-3525: ------------------------------------------- I whole disagree - enable early access cannot be just "which updates sites are present") - it is *solely* about wether we show earlyaccess or not and we always have to have a way to turn it on/off globally so we can remove all affected earlyaccess update sites. check for updates should not do anything different than what a normal check for updates does IMO. If you have not actually installed anything from an earlyaccess site you should not be getting updates imo. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:33:01 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 06:33:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118085#comment-13118085 ] Mickael Istria commented on JBDS-3525: -------------------------------------- {quote}I whole disagree - enable early access cannot be just "which updates sites are present") - it is solely about wether we show earlyaccess or not and we always have to have a way to turn it on/off globally so we can remove all affected earlyaccess update sites.{quote} Right, this is the current implementation. But it doesn't seem to match what users, and even [~akazakov] who's a JBT expert, understand and expect from the UI. {qupte}check for updates should not do anything different than what a normal check for updates does IMO. If you have not actually installed anything from an earlyaccess site you should not be getting updates imo.{quote} I agree, and this is the current state. The confusing user story is a user clicking "enable early-access" then "Check for updates" expects to see newer early-access content. It's not what's happening right now. I suggest we add it to the topics for JBIDE-20609 > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:39:01 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 06:39:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early-Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118090#comment-13118090 ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- [~akazakov] [~fbricon] Is it a good candidate for 4.3.1 ? > More accessible and visible Early-Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.x > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:40:00 2015 From: issues at jboss.org (=?UTF-8?Q?Andrej_=C5=A0migala_=28JIRA=29?=) Date: Wed, 14 Oct 2015 06:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118093#comment-13118093 ] Andrej ?migala commented on JBDS-3537: -------------------------------------- [~mickael_istria] No, I can no loger reproduce it. > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:40:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 06:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim In-Reply-To: References: Message-ID: Jan Richter created JBIDE-20945: ----------------------------------- Summary: UI scaling messes up the address bar in BrowserSim Key: JBIDE-20945 URL: https://issues.jboss.org/browse/JBIDE-20945 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Affects Versions: 4.3.0.Final Reporter: Jan Richter Attachments: browsersim.png Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. Here is a screenshot from Windows: !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:49:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 14 Oct 2015 06:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov reassigned JBIDE-20945: ---------------------------------------------- Assignee: Konstantin Marmalyukov > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:52:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 14 Oct 2015 06:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118106#comment-13118106 ] Konstantin Marmalyukov commented on JBIDE-20945: ------------------------------------------------ [~jrichter1] Jan, what does "scale factor" means? Screen resolution or what? I will appreciate steps how to set it on windows or Fedora :) > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:54:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 06:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118109#comment-13118109 ] Max Rydahl Andersen commented on JBDS-3525: ------------------------------------------- Am I missing something but why should check for updates give newer content today ? we don't have any overlaps today between GA and EA today ? Even if we had, I do not think it is proper to go add all earlyaccess sites when EA enabled since then you would get changes even if you hadn't even decided to install anything from the earlyaccess yet. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:54:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 06:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118110#comment-13118110 ] Max Rydahl Andersen commented on JBDS-3525: ------------------------------------------- Maybe call it "Show earlyaccess" ? > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 06:58:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 14 Oct 2015 06:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118117#comment-13118117 ] Andrej Podhradsky commented on JBDS-3537: ----------------------------------------- Neither do I. > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:04:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 07:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118124#comment-13118124 ] Jan Richter commented on JBIDE-20945: ------------------------------------- UI Scale factor is generally about "how big the items on screen are relative to their original size", so you can have your UI enlarged n times. Comes in handy on really big resolution, otherwise everything would be tiny. With Gnome, you can set it with this command (n = scaling multiplier): {code}gsettings set org.gnome.desktop.interface scaling-factor n{code} On Windows, you just need to go to "Display Settings" and adjust the Size settings. > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:05:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 07:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118124#comment-13118124 ] Jan Richter edited comment on JBIDE-20945 at 10/14/15 7:04 AM: --------------------------------------------------------------- UI Scale factor is generally about "how big the items on screen are relative to their original size" (which means factor of 1), so you can have your UI enlarged n times. Comes in handy on really big resolution, otherwise everything would be tiny. With Gnome, you can set it with this command (n = scaling multiplier): {code}gsettings set org.gnome.desktop.interface scaling-factor n{code} On Windows, you just need to go to "Display Settings" and adjust the Size settings. was (Author: jrichter1): UI Scale factor is generally about "how big the items on screen are relative to their original size", so you can have your UI enlarged n times. Comes in handy on really big resolution, otherwise everything would be tiny. With Gnome, you can set it with this command (n = scaling multiplier): {code}gsettings set org.gnome.desktop.interface scaling-factor n{code} On Windows, you just need to go to "Display Settings" and adjust the Size settings. > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:31:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 14 Oct 2015 07:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-521) Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-521: --------------------------------------- Summary: Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral Key: JBTIS-521 URL: https://issues.jboss.org/browse/JBTIS-521 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 9.0.0.Alpha2 Environment: JBDS 9.0.0.GA Reporter: Andrej Podhradsky Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral. In Preferences > Available Software Sites I see the following sites - Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/ - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess/ The correct sites should be - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ - https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:32:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 14 Oct 2015 07:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-521) Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-521: ------------------------------------ Description: Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral. In Preferences > Available Software Sites I see the following sites - https://devstudio.redhat.com/9.0/stable/updates/ - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/ - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess/ The correct sites should be - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ - https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ was: Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral. In Preferences > Available Software Sites I see the following sites - Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/ - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess/ The correct sites should be - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ - https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral > ------------------------------------------------------------------------------- > > Key: JBTIS-521 > URL: https://issues.jboss.org/browse/JBTIS-521 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Environment: JBDS 9.0.0.GA > Reporter: Andrej Podhradsky > > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral. In Preferences > Available Software Sites I see the following sites > - https://devstudio.redhat.com/9.0/stable/updates/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess/ > The correct sites should be > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:37:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 07:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118141#comment-13118141 ] Max Rydahl Andersen commented on JBIDE-20945: --------------------------------------------- [~jrichter1] can you add a label or an overall jira that you link these issues with respect to scaling together with ? I'm not sure how much of this we can fix without changes to SWT upstream but if we do find a solution it would be good to be able to check for the cases we've already identified as problematic. > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:48:01 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 07:48:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118147#comment-13118147 ] Mickael Istria commented on JBDS-3525: -------------------------------------- {quote}Maybe call it "Show earlyaccess" ?{quote} Except that when unticking, it removes the early-access sites. So it would also confuse users ;) > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:48:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 07:48:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118149#comment-13118149 ] Alexey Kazakov commented on JBDS-3525: -------------------------------------- If we called it Show EA, instead of Enable EA, I wasn't so confused ;-) IMO 'Show EA' would reflect our current functionality more correctly. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:50:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 07:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118165#comment-13118165 ] Max Rydahl Andersen commented on JBDS-3525: ------------------------------------------- No, unclicking "Show earlyaccess" fits perfectly with removing early access site since if they are not removed we would still show them earlyaccess content when running check for update. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 07:54:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 07:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118149#comment-13118149 ] Alexey Kazakov edited comment on JBDS-3525 at 10/14/15 7:53 AM: ---------------------------------------------------------------- If we called it Show EA, instead of Enable EA, I wouldn't be so confused ;-) IMO 'Show EA' would reflect our current functionality more correctly. was (Author: akazakov): If we called it Show EA, instead of Enable EA, I wasn't so confused ;-) IMO 'Show EA' would reflect our current functionality more correctly. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:00:04 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 08:00:04 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBIDE-20945: -------------------------------- Labels: ui-scaling (was: ) > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Labels: ui-scaling > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:01:01 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 08:01:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBDS-3539: ------------------------------ Labels: ui-scaling (was: ) > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui-scaling > Fix For: 9.0.1.GA, 9.1.0.GA, 10.0.0.Alpha1 > > Attachments: 4kInstaller.png, step2.png, step3.png, step4.png, step5.png, step6.png, step7.png, step8.png, step9.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:01:02 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 08:01:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBIDE-20935: -------------------------------- Labels: ui-scaling (was: ) > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:01:02 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 08:01:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3542) Splash screen scaling is broken on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Richter updated JBDS-3542: ------------------------------ Labels: ui-scaling (was: ) > Splash screen scaling is broken on Windows > ------------------------------------------ > > Key: JBDS-3542 > URL: https://issues.jboss.org/browse/JBDS-3542 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: ui/branding > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 4k resolution with 250% scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: splash.png > > > The splash screen window itself doesn't scale, but some text inside it does. The result looks like this: > !splash.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:26:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 08:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-521) Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-521: -------------------------------- Assignee: Paul Leacu > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral > ------------------------------------------------------------------------------- > > Key: JBTIS-521 > URL: https://issues.jboss.org/browse/JBTIS-521 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Environment: JBDS 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral. In Preferences > Available Software Sites I see the following sites > - https://devstudio.redhat.com/9.0/stable/updates/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess/ > The correct sites should be > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:26:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 08:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-520: -------------------------------- Assignee: Paul Leacu > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:34:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 14 Oct 2015 08:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117427#comment-13117427 ] Andre Dietisheim edited comment on JBIDE-19178 at 10/14/15 8:33 AM: -------------------------------------------------------------------- In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. * Applications ** Foo (the application root node; properties view might contain services and routes with actions like, open in browser) *** instance-1 (an instance of the application, i.e. the container running the application) *** instance-2 *** OpenShift **** ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: * root ** Deployments *** Deployment-a **** pod-a ***** instance 1 ****** container 1 (properties might show the specific build) **** pod-b ** Services *** service-a (properties view might expose related routes) ** Builds *** Config-a **** build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). {quote} was (Author: adietish): In a mail from [~rcernich] on the 10th of September "JBoss Tools OpenShift Server Integration" {quote} The server framework in Eclipse has two main features: * Deployment - running a project on a server * Servers View - visualizing details about a server and facilitating management of the server OpenShift is an intersting type of "server" since it's more of a platform for running servers (a server server?). That said, it can be configured to support running specific types of user applications (projects?) through the use of builder images and templates. Given that, I think there is an opportunity to use the capabilities feature within the servers framework to support the "Run on Server" functionality for OpenShift. For example, if an OpenShift instance has the EAP, JWS and Ruby builder images installed, that OS instance can be marked as supporting EAP, JWS and Ruby project types. (EAP and JWS are a bit peculiar since they support JEE project types, but you get the gist.) This can then be used to integrate other aspects of the servers framework for OS. At this point, I don't think we should get lost in the details regarding pods, containers, etc., but should keep it simple, similar to the basic new-app functionality: an app is a project and has a single service, a single dc with a single pod template (for those that need concrete, implementation details). The user doesn't really need to know or care about what an application is, or that it's composed of these various objects within OS. (We need to know this, but they don't.) I won't get into this any further, as that was the purpose of my other email (what is required to support "run on server" for OS). This pretty much covers the "deployment" case. The servers view is more interesting because there are a few different approaches you can take to visualizing an OS instance: * object views (pods, dcs, etc.) * application views (don't shoot!) * node views (really just a container for object or application views) >From an application developer's perspective, I don't think they should care about pods, services, dcs, etc. They care about building an application. The ops guys care about how/where it ends up running. Because of this, I think forcing concepts like pods, etc. onto the application developer is not the best way to go as it's confusing and is pretty much orthogonal to their job responsibilities. Given that, I'm a proponent of an application view, however application isnt' a clearly defined term within OS (a separate discussion). Putting the general view concepts aside, we can focus on container objects running xpaas images (e.g. eap, jws, etc.). If a container is running one of these images, we should be able to provide the same view below that container node that we provide for an eap, jws, etc. server in the servers view. These views would be specific to each container running the image (in the event replicas > 1). Diving into an "application view," in lieu of a concrete definition of application in openshift, I will propose a few definitions, for the purpose of advancing the tools: * All objects with the same value for an "application" label, e.g. application=foo == the foo application. More generically, an application view could simply be a filtered view based on label key/value pairs, e.g. show all objects with label application=foo || deploymentConfig=bar. * A dc or rc, along with all objects referencing the dc, or objects within it. For example, a dc, (dc-a) includes a pod template (pt-b) referencing an image (ist-c) built by a bc (bc-d), which is referenced by a service (s-e) through a label and is exposed via a route (r-f). In this example, you'd assume the application is: dc dc-a, all deployments created from dc-a, all pods created from pt-b, image stream is-c, build config bc-d, all builds from bc-d, service s-e and route r-f. Note, given the relationship between services and pods that it's possible a single service could be a part of many "applications." Any objects not associated with a dc could be displayed in a "misc" or "raw" view (the latter could contain all objects, even if they're part of an "application"). What that might look like in a view: A dc based application view. * Applications ** Foo (the application root node; properties view might contain services and routes with actions like, open in browser) *** instance-1 (an instance of the application, i.e. the container running the application) *** instance-2 *** OpenShift **** ...related OpenShift objects, organized as they would be for a generic OpenShift view. A labels filter based approach: * root ** Deployments *** Deployment-a **** pod-a ***** instance 1 ****** container 1 (properties might show the specific build) ***** pod-b ** Services *** service-a (properties view might expose related routes) ** Builds *** Config-a **** build-1 Hopefully, that's enough to give you some idea what I'm thinking. I don't know how this aligns with others' views on the subject. I suspect there's some overlap with what's displayed in the OS console too (which might also want to consider alternate views structured for application developers as opposed to operations folks). {quote} > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:38:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 08:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20797) CCE on first start on clean install of CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118196#comment-13118196 ] patrik suzzi commented on JBIDE-20797: -------------------------------------- I verified the same error happens on Eclipse Mars.1 + JBossTools 4.3.0 Final I'm sure the fix will be applied for 4.5.1 Maintenance too, isn'it? > CCE on first start on clean install of CR1 > ------------------------------------------ > > Key: JBIDE-20797 > URL: https://issues.jboss.org/browse/JBIDE-20797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > clean install of eclipse JEE + CR1 jbosstools for mars. > Get this error on startup on a clean workspace: > {code} > java.lang.ClassCastException: [Lorg.eclipse.swt.graphics.FontData; cannot be cast to java.lang.String > at org.eclipse.ui.internal.themes.Theme$1.propertyChange(Theme.java:124) > at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:351) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:347) > at org.eclipse.jface.preference.PreferenceConverter.setValue(PreferenceConverter.java:463) > at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.ensurePreferenceStoreBackwardsCompatibility(JavaScriptPlugin.java:395) > at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.start(JavaScriptPlugin.java:336) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318) > at org.eclipse.osgi.container.Module.doStart(Module.java:571) > at org.eclipse.osgi.container.Module.start(Module.java:439) > at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454) > at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327) > at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.editorOpened(JavaEditorTracker.java:157) > at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.partOpened(JavaEditorTracker.java:152) > at org.eclipse.ui.internal.WorkbenchPage$18.run(WorkbenchPage.java:4939) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartOpened(WorkbenchPage.java:4936) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$2.handleEvent(CompatibilityPart.java:121) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > 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.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > 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.e4.ui.model.application.ui.basic.impl.PartImpl.setObject(PartImpl.java:410) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:131) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:99) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > 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.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > 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.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:494) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:458) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:724) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:396) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1166) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3234) > at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3149) > at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3131) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3126) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3090) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3071) > at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:436) > at org.jboss.tools.central.JBossCentralActivator$6$1.run(JBossCentralActivator.java:411) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > 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:483) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:44:01 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 08:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] patrik suzzi updated JBIDE-20935: --------------------------------- Attachment: JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 Reproducible in win8.1 too > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:46:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 08:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118202#comment-13118202 ] patrik suzzi edited comment on JBIDE-20935 at 10/14/15 8:45 AM: ---------------------------------------------------------------- Reproducible in win8.1 too [^JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4] was (Author: patriksuzzi): Reproducible in win8.1 too > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:46:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 08:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118202#comment-13118202 ] patrik suzzi edited comment on JBIDE-20935 at 10/14/15 8:45 AM: ---------------------------------------------------------------- Reproducible in win8.1 too [^JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4] [link title|http://example.com] was (Author: patriksuzzi): Reproducible in win8.1 too [^JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4] > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:47:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 08:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118202#comment-13118202 ] patrik suzzi edited comment on JBIDE-20935 at 10/14/15 8:46 AM: ---------------------------------------------------------------- Reproducible in win8.1 too [^JBossCentral_not-rescaling.mp4] was (Author: patriksuzzi): Reproducible in win8.1 too [^JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4] [link title|http://example.com] > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:48:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 08:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118202#comment-13118202 ] patrik suzzi edited comment on JBIDE-20935 at 10/14/15 8:47 AM: ---------------------------------------------------------------- Reproducible in win8.1 too [JBoss Central not rescaling (mp4, 370kb)|^JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4] was (Author: patriksuzzi): Reproducible in win8.1 too [^JBossCentral_not-rescaling.mp4] > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:49:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 08:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118202#comment-13118202 ] patrik suzzi edited comment on JBIDE-20935 at 10/14/15 8:48 AM: ---------------------------------------------------------------- Reproducible in win8.1 too, see: [JBoss Central doesn't scale (mp4, 370k)|^JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4] was (Author: patriksuzzi): Reproducible in win8.1 too [JBoss Central not rescaling (mp4, 370kb)|^JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4] > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:59:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 14 Oct 2015 08:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118209#comment-13118209 ] Fred Bricon commented on JBIDE-20935: ------------------------------------- [~kmarmaliykov], [~ibuziuk]: any idea? > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:05:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 09:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118214#comment-13118214 ] Jeff Cantrill commented on JBIDE-19178: --------------------------------------- [~maxandersen] It's not clear to me how this now mock up differs from the original one I proposed. I thought your concerns with the original proposal was that there was too much 'tree' in the overall view, and that it would be cleaner to limit the explorer view to minimal amount of resource info. The supporting resources and details (e.g. deployments, builds) would be represented in a tab of the properties view. I think this approach would make the explorer look MUCH more like v2 and off load many of the other details into properties. I image this approach would give you something simple like: {noformat} service (route) |-pod {noformat} My biggest issue is that all the supporting details would be in a properties view, but maybe that doesn't matter since we are trying to hide them (sort of) from the developer. I do think something like builds are of interest and maybe that is a 'right-click' on the 'app(service)' to open the properties view. Also, we do have an open issue (I believe) to add label filtering to the current view which would make sense to carry over into this one. > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:10:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 09:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118220#comment-13118220 ] patrik suzzi commented on JBIDE-20935: -------------------------------------- Loos like a layouting problem for the tab containing the Browser element. It can be solved by using a proper layout or rescaling. If not possible, a workaround can be to listen to the resize layout (but I don't like this solution that much) But there is another question: Is this happening only in windows, really ? > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:29:00 2015 From: issues at jboss.org (Jiri Peterka (JIRA)) Date: Wed, 14 Oct 2015 09:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118231#comment-13118231 ] Jiri Peterka commented on JBDS-3537: ------------------------------------ Works good for me as well. > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:34:00 2015 From: issues at jboss.org (Jan Richter (JIRA)) Date: Wed, 14 Oct 2015 09:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118238#comment-13118238 ] Jan Richter commented on JBIDE-20935: ------------------------------------- It doesn't happen on my Fedora and I didn't have a chance to test it on a mac. > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:35:00 2015 From: issues at jboss.org (Jiri Peterka (JIRA)) Date: Wed, 14 Oct 2015 09:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118231#comment-13118231 ] Jiri Peterka edited comment on JBDS-3537 at 10/14/15 9:34 AM: -------------------------------------------------------------- Works good for me as well (Brno office location) was (Author: jpeterka): Works good for me as well. > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:36:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Wed, 14 Oct 2015 09:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118239#comment-13118239 ] Ilya Buziuk commented on JBIDE-20935: ------------------------------------- Hmmm... Looks weird. Assuming that central is written on HTML5 and it has responsive design, it might be that js detects that window size was not changed after restoring > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:40:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Wed, 14 Oct 2015 09:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118243#comment-13118243 ] Ilya Buziuk commented on JBIDE-20935: ------------------------------------- < It doesn't happen on my Fedora and I didn't have a chance to test it on a mac. than it must be coupled with IE. As I recall on Fedora and Mac SWT.Webkit is used as a browser engine, for windows it's SWT.IE. It looks like ie can not handle some js / css layout > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:41:00 2015 From: issues at jboss.org (Jiri Peterka (JIRA)) Date: Wed, 14 Oct 2015 09:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118244#comment-13118244 ] Jiri Peterka commented on JBDS-3538: ------------------------------------ I'm not experiencing any described issues today, everything goes fast and smoothly for me (located in Brno/CZ office). > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:44:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 14 Oct 2015 09:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118248#comment-13118248 ] Nick Boldt commented on JBTIS-520: ---------------------------------- So you want to call the IS Alpha2 bits "stable" when most of them are Alpha or Beta? Why shouldn't we use the /development/ site when the content is still a pre-GA milestone? > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:48:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 09:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118249#comment-13118249 ] Paul Leacu commented on JBTIS-520: ---------------------------------- [~maxandersen] [~nickboldt] [~akazakov] Before I commit - here's what I've done: * Established a stable IS composite site for the GA'd bits (SOA 5.x compat plugins) https://devstudio.redhat.com/9.0/stable/updates/integration-stack/ * Established JBDSIS 9.0.0.GA which contains only the non EA plugins (couldn't continue to call it 9.0.0.Alpha2 right?) * Established a stable IS discovery site: https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discovery/ * Tested like this: * {code} ./jbdevstudio -vmargs -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discovery/ {code} No development URL appears after installing SOA 5.x compat plugins. Please be specific if this is incorrect. Thankyou > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:50:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Wed, 14 Oct 2015 09:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118250#comment-13118250 ] Konstantin Marmalyukov commented on JBIDE-20935: ------------------------------------------------ It's not IE problem, it's Central view problem. I try other cases: - internal web browser and openshift-hosted central webpage - locally imported central webpage and preview tab of visual editor Everything works fine. Issue looks very strange - when I simply resize Central view everything is fine, but when I either maximize Central view or minimize any neighbor view like Patrik does I have the error. > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4 > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 09:51:00 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 09:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] patrik suzzi updated JBIDE-20935: --------------------------------- Attachment: screenshot-1.png > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, screenshot-1.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 10:00:01 2015 From: issues at jboss.org (patrik suzzi (JIRA)) Date: Wed, 14 Oct 2015 10:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118258#comment-13118258 ] patrik suzzi commented on JBIDE-20935: -------------------------------------- I would consider the fact we have two tabs (on the bottom) Look at the screenshoot, !screenshot-1.png|thumbnail! The inner area of the tab containing the browser is given a "wrong size" after scaling. My theory: The component containing the browser is not resized properly after resizing the view, in windows. > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, screenshot-1.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 10:28:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 10:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-520: ----------------------------- Attachment: non-ea.png > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: non-ea.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 10:29:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 10:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118249#comment-13118249 ] Paul Leacu edited comment on JBTIS-520 at 10/14/15 10:28 AM: ------------------------------------------------------------- [~maxandersen] [~nickboldt] [~akazakov] Before I commit - here's what I've done: * Established a stable IS composite site for the GA'd bits (SOA 5.x compat plugins) https://devstudio.redhat.com/9.0/stable/updates/integration-stack/ * Established JBDSIS 9.0.0.GA which contains only the non EA plugins (couldn't continue to call it 9.0.0.Alpha2 right?) * Established a stable IS discovery site: https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discovery/ * Tested like this: * {code} ./jbdevstudio -vmargs -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discovery/ {code} No development URL appears after installing SOA 5.x compat plugins. See !non-ea.png|thumbnail! Please be specific if this is incorrect. Thankyou was (Author: pleacu): [~maxandersen] [~nickboldt] [~akazakov] Before I commit - here's what I've done: * Established a stable IS composite site for the GA'd bits (SOA 5.x compat plugins) https://devstudio.redhat.com/9.0/stable/updates/integration-stack/ * Established JBDSIS 9.0.0.GA which contains only the non EA plugins (couldn't continue to call it 9.0.0.Alpha2 right?) * Established a stable IS discovery site: https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discovery/ * Tested like this: * {code} ./jbdevstudio -vmargs -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discovery/ {code} No development URL appears after installing SOA 5.x compat plugins. Please be specific if this is incorrect. Thankyou > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: non-ea.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 10:33:00 2015 From: issues at jboss.org (Victor Rubezhny (JIRA)) Date: Wed, 14 Oct 2015 10:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20797) CCE on first start on clean install of CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118280#comment-13118280 ] Victor Rubezhny commented on JBIDE-20797: ----------------------------------------- [~patriksuzzi] The fix for [https://bugs.eclipse.org/bugs/show_bug.cgi?id=468796|Bug #468796] is applied for 4.5.2 (as Bugzilla states). It's too late for Mars.1. > CCE on first start on clean install of CR1 > ------------------------------------------ > > Key: JBIDE-20797 > URL: https://issues.jboss.org/browse/JBIDE-20797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > clean install of eclipse JEE + CR1 jbosstools for mars. > Get this error on startup on a clean workspace: > {code} > java.lang.ClassCastException: [Lorg.eclipse.swt.graphics.FontData; cannot be cast to java.lang.String > at org.eclipse.ui.internal.themes.Theme$1.propertyChange(Theme.java:124) > at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:351) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:347) > at org.eclipse.jface.preference.PreferenceConverter.setValue(PreferenceConverter.java:463) > at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.ensurePreferenceStoreBackwardsCompatibility(JavaScriptPlugin.java:395) > at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.start(JavaScriptPlugin.java:336) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318) > at org.eclipse.osgi.container.Module.doStart(Module.java:571) > at org.eclipse.osgi.container.Module.start(Module.java:439) > at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454) > at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327) > at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.editorOpened(JavaEditorTracker.java:157) > at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.partOpened(JavaEditorTracker.java:152) > at org.eclipse.ui.internal.WorkbenchPage$18.run(WorkbenchPage.java:4939) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartOpened(WorkbenchPage.java:4936) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$2.handleEvent(CompatibilityPart.java:121) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > 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.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > 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.e4.ui.model.application.ui.basic.impl.PartImpl.setObject(PartImpl.java:410) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:131) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:99) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > 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.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > 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.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:494) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:458) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:724) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:396) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1166) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3234) > at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3149) > at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3131) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3126) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3090) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3071) > at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:436) > at org.jboss.tools.central.JBossCentralActivator$6$1.run(JBossCentralActivator.java:411) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > 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:483) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 10:35:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 10:35:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118281#comment-13118281 ] Alexey Kazakov commented on JBTIS-520: -------------------------------------- Looks good. But we also need to include https://devstudio.redhat.com/9.0/stable/updates/integration-stack/ into https://devstudio.redhat.com/9.0/stable/updates/compositeArtifacts.xml And use our main updatesite https://devstudio.redhat.com/9.0/stable/updates/ in https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: non-ea.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 10:37:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 14 Oct 2015 10:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118285#comment-13118285 ] Fred Bricon commented on JBIDE-20935: ------------------------------------- FTR, I got no issue on Mac > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Labels: ui-scaling > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, screenshot-1.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:26:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 11:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-520: ----------------------------- Attachment: non-ea2.png > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:26:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 11:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118315#comment-13118315 ] Paul Leacu commented on JBTIS-520: ---------------------------------- Done https://github.com/jbdevstudio/jbdevstudio-website/commit/ccd0e7d718b369c50c522e3768b46d5c8d885e65 This is what you see now: !non-ea2.png|thumbnail! > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:34:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 11:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118318#comment-13118318 ] Alexey Kazakov commented on JBTIS-520: -------------------------------------- Looks good. But need to be tested. [~ldimaggio]? > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:41:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 14 Oct 2015 11:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118323#comment-13118323 ] Max Rydahl Andersen commented on JBTIS-520: ------------------------------------------- [~nickboldt] none of the alpha/beta should be provided on JBDS 9, only earlyaccess, right ? The stable site should be empty if they don't have anything ready for GA. we have one long standing absolute rule - no jboss.org in devstudio updatesites, nor no mixing of development sites into to stable streams. > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:44:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 14 Oct 2015 11:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20609: ------------------------------- Summary: More accessible and visible Early Access content (was: More accessible and visible Early-Access content) > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.x > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:50:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 11:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118330#comment-13118330 ] Mickael Istria commented on JBDS-3525: -------------------------------------- Changes to improve user experience on Install/Software pages are tracked on JBIDE-20609 . > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:51:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 11:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria closed JBDS-3525. -------------------------------- Resolution: Cannot Reproduce So far, we don't manage to reproduce this issue. It appears like this was a temporary issue with our download server. Feel free to reopen if you mange to reproduce it, using the steps to reproduce reported to this ticket. > Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-3525 > URL: https://issues.jboss.org/browse/JBDS-3525 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.0.0.Beta2 > Environment: Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > Enabled Early Access > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > Attachments: arquillian-in-jbt.png, updates-sites.xml > > > JBDS notified me about a new update for Arquillian, but then after going into update it complains about: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 11:57:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 11:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3537) Connection problems with https://devstudio.jboss.com/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria closed JBDS-3537. -------------------------------- Resolution: Cannot Reproduce Bug Seems like this was a temporary issue. All recent tentatives from several corners of the planet have succeeded in the last days. Let's blame Akamai, and hope this is really a temporary issue that won't happen again. > Connection problems with https://devstudio.jboss.com/ > ----------------------------------------------------- > > Key: JBDS-3537 > URL: https://issues.jboss.org/browse/JBDS-3537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.GA, 10.0.0.Alpha1 > > > Recently, I have connection problems with https://devstudio.jboss.com/ > For example, I tried to install BYOE from https://devstudio.redhat.com/9.0/stable/updates/ into my Eclipse Mars JEE and I got errors such as > Unable to read repository at https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/plugins/tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar. > Or when I tried to install JBDS-IS into JBDS 8.1.0.GA I got error > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://devstudio.redhat.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-updatesite-core/content.jar > Note that all mentioned jar files are available, but not always. I tried to download them via wget from command line and after several tries I got read error. > Does someone else has similar problem like me? (note: I'm in Brno) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 12:46:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Wed, 14 Oct 2015 12:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio updated JBTIS-520: ------------------------------- Attachment: 3.png 2.png 1.png See the attached screenshots - the files are named 1.png, 2.png, 3.png 1.png - Only one update site is available 2.png - Why is nothing available for IS? 3.png - -With EA enabled - still only 1 site available Is this what we expect to see?? > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: 1.png, 2.png, 3.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 13:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118363#comment-13118363 ] Alexey Kazakov commented on JBTIS-520: -------------------------------------- 1. Yes, this what is expected. Only one update site is available. 2. There is SOA available. If it's GA ready then it's OK. The rest (not GA ready IS stuff should be available in EA only). 3. This is confusion we have discussed in JBDS-3525 (see the last few comments). We add EA update site only when you installed something from EA. If you just check "Enable EA" in central but didn't really install anything yet from it then we don't add the update site. So, "Show EA" would be better than "Enable EA" actually. We will continue discuss how we can improve EA central in JBIDE-20609 > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: 1.png, 2.png, 3.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:09:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Wed, 14 Oct 2015 13:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20368) Icons in Batch flow editor are partially not visible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118365#comment-13118365 ] Snjezana Peco commented on JBIDE-20368: --------------------------------------- I have created a workaround for https://bugs.eclipse.org/bugs/show_bug.cgi?id=466099. > Icons in Batch flow editor are partially not visible > ---------------------------------------------------- > > Key: JBIDE-20368 > URL: https://issues.jboss.org/browse/JBIDE-20368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Affects Versions: 4.3.0.Beta2 > Environment: Linux, GTK3 or GTK2 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.3.x > > Attachments: BatchGTK2.png, BatchGTK3.png > > > Icons (Zoom in/out/actual, save as image, print) are partially hidden. See screenshots. > I'm on Linux (Fedora 22). I've tried both GTK3 (3.16.5) and GTK2 (2.24.28). > GTK3: > !BatchGTK3.png! > GTK2: > !BatchGTK2.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:25:00 2015 From: issues at jboss.org (Viacheslav Kabanovich (JIRA)) Date: Wed, 14 Oct 2015 13:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118370#comment-13118370 ] Viacheslav Kabanovich commented on JBIDE-20927: ----------------------------------------------- Then, let us add jst jsf plugins to jst.web.kb.test plugin with test that checks that validators exist and are ignored. > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:38:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118376#comment-13118376 ] Denis Golovin commented on JBIDE-20927: --------------------------------------- IMO to run tests in environment that is really close to real installation it is better to have additional bundles installed through surefire plugin configuration. > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:40:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20366) Easymport should offer available m2e connectors when importing Maven projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20366: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.x) > Easymport should offer available m2e connectors when importing Maven projects > ----------------------------------------------------------------------------- > > Key: JBIDE-20366 > URL: https://issues.jboss.org/browse/JBIDE-20366 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.1.Final > > > For example standard maven import offers tycho connector installation for a user. Easymport should provide the same user comfort as maven import does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:50:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 13:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20366) Easymport should offer available m2e connectors when importing Maven projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-20366: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Easymport should offer available m2e connectors when importing Maven projects > ----------------------------------------------------------------------------- > > Key: JBIDE-20366 > URL: https://issues.jboss.org/browse/JBIDE-20366 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > For example standard maven import offers tycho connector installation for a user. Easymport should provide the same user comfort as maven import does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:52:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 13:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-19768: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Add possibility to select which nested projects to import > --------------------------------------------------------- > > Key: JBIDE-19768 > URL: https://issues.jboss.org/browse/JBIDE-19768 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import. > Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 13:52:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 14 Oct 2015 13:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19765) Add description to easy import wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-19765: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Add description to easy import wizard > ------------------------------------- > > Key: JBIDE-19765 > URL: https://issues.jboss.org/browse/JBIDE-19765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: wizard.png > > > There is no descrption of the wizard (see picture attached). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:11:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- Fix Version/s: 9.0.1.GA (was: 9.0.x) (was: 9.x) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:11:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:11:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- Status: New (was: New) Target Release: 9.0.1.GA > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:12:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3535: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:12:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:01 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 14:12:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-520: ----------------------------- Attachment: ea.png > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, ea.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:01 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Wed, 14 Oct 2015 14:12:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio updated JBTIS-520: ------------------------------- Attachment: 5.png 4.png 4.png - After installing from EA 5.png - We see the additional update site Yes - this is confusing! Can we at least document this?? > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, ea.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:12:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:12:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3543) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: Denis Golovin created JBDS-3543: ----------------------------------- Summary: Installer progress looks bad with OS X El Capitan Key: JBDS-3543 URL: https://issues.jboss.org/browse/JBDS-3543 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 9.0.0.CR2 Reporter: Martin Malina Assignee: Daniel Azarov Fix For: 9.0.1.GA It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). It is now a narrow stripe and the text that we display over it does not look nice. !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:13:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3543) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3543: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3543 > URL: https://issues.jboss.org/browse/JBDS-3543 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:13:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3543) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3543: -------------------------------- Fix Version/s: 9.1.0.GA (was: 9.0.1.GA) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3543 > URL: https://issues.jboss.org/browse/JBDS-3543 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.GA > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:16:01 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 14:16:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118387#comment-13118387 ] Paul Leacu commented on JBTIS-520: ---------------------------------- Hey Len - I was updating things just now. Basically you should just see !non-ea2.png|thumbnail! after installing the IS SOA 5.x Dev plugins and you should see !ea.png|thumbnail! after enabling early access and installing EA IS plugins. No IS URLS appear. > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, ea.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:17:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3543) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3543: -------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.GA) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3543 > URL: https://issues.jboss.org/browse/JBDS-3543 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 10.0.0.Alpha1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:17:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3543) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3543: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3543 > URL: https://issues.jboss.org/browse/JBDS-3543 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 10.0.0.Alpha1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:17:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3543) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3543: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3543 > URL: https://issues.jboss.org/browse/JBDS-3543 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 10.0.0.Alpha1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:17:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3543) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3543: -------------------------------- Target Release: 10.0.0.GA (was: 9.0.1.GA) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3543 > URL: https://issues.jboss.org/browse/JBDS-3543 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 10.0.0.Alpha1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:23:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 14 Oct 2015 14:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-521) Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-521. ------------------------------ Fix Version/s: 9.0.0.Alpha2 Resolution: Duplicate Issue See https://issues.jboss.org/browse/JBTIS-520 > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral > ------------------------------------------------------------------------------- > > Key: JBTIS-521 > URL: https://issues.jboss.org/browse/JBTIS-521 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Environment: JBDS 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.0.Alpha2 > > > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral. In Preferences > Available Software Sites I see the following sites > - https://devstudio.redhat.com/9.0/stable/updates/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess/ > The correct sites should be > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:27:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (LOCUS-47) Locus plug-ins have errors after importing into workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/LOCUS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated LOCUS-47: ------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-locus/pull/46) > Locus plug-ins have errors after importing into workspace > --------------------------------------------------------- > > Key: LOCUS-47 > URL: https://issues.jboss.org/browse/LOCUS-47 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 1.3.0 > > > There are several problems with locus plrojects after importing them into workspace as maven projects: > 1. plugins/pom.xml appears in workspace with name "plugins" and it could conflict with other imported modules because we have the same names all over jbosstools; > 2. org.jboss.tools.locus.mockito uses restricted API and JDT reports it as Error; > 3. org.jboss.tools.locus.dmr export packages that created during maven build and reported as missing in eclipse. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:42:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- Fix Version/s: 9.1.0.Beta1 (was: 9.0.1.GA) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:42:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19846) Remove generated files after user decides to delete imported unuseful root In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-19846: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.x) > Remove generated files after user decides to delete imported unuseful root > -------------------------------------------------------------------------- > > Key: JBIDE-19846 > URL: https://issues.jboss.org/browse/JBIDE-19846 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.1.Final > > > When user selects folder root that contains no real data (e.g. workspace root) importer asks if he wants to delete the project after import. However, even if the project is deleted from workspace, the generated files (e.g .settings, .project) still remain on the filesystem. These should be deleted as they are clearly not needed nor desired. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:42:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:42:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 14 Oct 2015 14:42:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3535: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:42:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 14:42:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBDS-3535: -------------------------------- Target Release: 9.1.0.GA (was: 9.0.1.GA) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:46:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Mars Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3245: --------------------------------- Summary: Improve Eclipse Mars Platform (was: Improve Eclipse Platform) > Improve Eclipse Mars Platform > ----------------------------- > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:46:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Mars Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3245: --------------------------------- Target Release: 9.1.0.GA (was: 10.0.0.GA) > Improve Eclipse Mars Platform > ----------------------------- > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.1.GA, 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:47:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Mars Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3245: --------------------------------- Fix Version/s: 9.1.0.GA (was: 10.0.0.GA) (was: 9.0.1.GA) > Improve Eclipse Mars Platform > ----------------------------- > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.1.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:48:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3544) Improve Eclipse Neon Platform In-Reply-To: References: Message-ID: Alexey Kazakov created JBDS-3544: ------------------------------------ Summary: Improve Eclipse Neon Platform Key: JBDS-3544 URL: https://issues.jboss.org/browse/JBDS-3544 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Components: integration, requirements Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 9.1.0.GA As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3544) Improve Eclipse Neon Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3544: --------------------------------- Target Release: 10.0.0.GA (was: 9.1.0.GA) > Improve Eclipse Neon Platform > ----------------------------- > > Key: JBDS-3544 > URL: https://issues.jboss.org/browse/JBDS-3544 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3544) Improve Eclipse Neon Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3544: --------------------------------- Fix Version/s: 10.0.0.GA (was: 9.1.0.GA) > Improve Eclipse Neon Platform > ----------------------------- > > Key: JBDS-3544 > URL: https://issues.jboss.org/browse/JBDS-3544 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:50:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3544) Improve Eclipse Neon Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3544: --------------------------------- Epic Name: Improve Eclipse Neon Platform (was: Improve Eclipse Platform) > Improve Eclipse Neon Platform > ----------------------------- > > Key: JBDS-3544 > URL: https://issues.jboss.org/browse/JBDS-3544 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 10.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:50:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3245) Improve Eclipse Mars Platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3245: --------------------------------- Epic Name: Improve Eclipse Mars Platform (was: Improve Eclipse Platform) > Improve Eclipse Mars Platform > ----------------------------- > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.1.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:52:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3507: --------------------------------- Component/s: upstream > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBDS-3507 > URL: https://issues.jboss.org/browse/JBDS-3507 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-certification, 3rd-party-dependencies, upstream > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Fix For: 9.0.x > > Attachments: terminal.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3507: ------------------------------------ Assignee: Daniel Azarov [~dazarov] please create a bugzilla for that issue and provide a patch. > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBDS-3507 > URL: https://issues.jboss.org/browse/JBDS-3507 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-certification, 3rd-party-dependencies, upstream > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Daniel Azarov > Fix For: 9.0.x, 10.x > > Attachments: terminal.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3507: --------------------------------- Fix Version/s: 10.x > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBDS-3507 > URL: https://issues.jboss.org/browse/JBDS-3507 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-certification, 3rd-party-dependencies, upstream > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Daniel Azarov > Fix For: 9.0.x, 10.x > > Attachments: terminal.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 14:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 14:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118400#comment-13118400 ] Alexey Kazakov commented on JBIDE-20927: ---------------------------------------- OK, let's add org.eclipse.jst.jsf.facelet.ui and org.eclipse.jst.jsf.ui to pom.xml for jst.web.kb.test > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20609: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 (was: 4.3.x) > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:19:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18722) Fixing Eclipse/Neon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-18722: ----------------------------------- Summary: Fixing Eclipse/Neon (was: Fixing Eclipse/Neon (+Mars SR2)) > Fixing Eclipse/Neon > ------------------- > > Key: JBIDE-18722 > URL: https://issues.jboss.org/browse/JBIDE-18722 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.4.0.Final > > > "container" issue for issues related to fixes important to get into Luna. > Please link your Eclipse/Mars issue to this one instead of using subtasks (edit this description). > Current open WTP bugs with patches waiting to be applied (copy from original issue without fixed): > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: Future > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 show in console. target: none > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=318670 - [Workbench] Not all settings copied when switching workspace and "Copy settings" marked -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:19:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18722) Fixing Eclipse/Neon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-18722: ----------------------------------- Fix Version/s: (was: 4.3.1.Final) > Fixing Eclipse/Neon > ------------------- > > Key: JBIDE-18722 > URL: https://issues.jboss.org/browse/JBIDE-18722 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.4.0.Final > > > "container" issue for issues related to fixes important to get into Luna. > Please link your Eclipse/Mars issue to this one instead of using subtasks (edit this description). > Current open WTP bugs with patches waiting to be applied (copy from original issue without fixed): > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: Future > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 show in console. target: none > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=318670 - [Workbench] Not all settings copied when switching workspace and "Copy settings" marked -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:20:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20940: ----------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.1.Final) > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:20:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20940) JST test errors on jenkins after recent commits In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20940. ---------------------------------- Resolution: Done > JST test errors on jenkins after recent commits > ----------------------------------------------- > > Key: JBIDE-20940 > URL: https://issues.jboss.org/browse/JBIDE-20940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {code}testCustomTagLibs(org.jboss.tools.jst.web.ui.test.JQuery14PaletteCATest) Time elapsed: 0.003 sec > Palette CA templates(org.jboss.tools.common.base.test.model.XProjectImportTestSetUp) Time elapsed: 0.57 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:28) > at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85) > at junit.extensions.TestSetup$1.protect(TestSetup.java:24) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Running org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.019 sec <<< FAILURE! - in org.jboss.tools.jst.web.ui.editor.test.JstJspAllTests > junit.framework.TestSuite at 30ffce35(org.jboss.tools.test.util.ProjectImportTestSetup) Time elapsed: 1.22 sec <<< ERROR! > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer$1.run(FormPropertySheetViewer.java:300) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.jboss.tools.test.util.xpl.DisplayHelper.driveEventQueue(DisplayHelper.java:228) > at org.jboss.tools.test.util.xpl.DisplayHelper.waitForCondition(DisplayHelper.java:60) > at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:95) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) > at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:32) > at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:324) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:87) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:21:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20828) Unify code for Link widget emulation via StyledText In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20828: ----------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.1.Final) > Unify code for Link widget emulation via StyledText > --------------------------------------------------- > > Key: JBIDE-20828 > URL: https://issues.jboss.org/browse/JBIDE-20828 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.3.1.Beta1 > > > Because of the upstream issue with link widgets that are not clickable (in dialogs only) we started emulating it via StyledText: JBIDE-20092, JBIDE-20361, https://bugs.eclipse.org/bugs/show_bug.cgi?id=471717 > We now should centralize the code that creates those StyledTexts -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:21:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20828) Unify code for Link widget emulation via StyledText In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20828. ---------------------------------- Resolution: Done > Unify code for Link widget emulation via StyledText > --------------------------------------------------- > > Key: JBIDE-20828 > URL: https://issues.jboss.org/browse/JBIDE-20828 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.3.1.Beta1 > > > Because of the upstream issue with link widgets that are not clickable (in dialogs only) we started emulating it via StyledText: JBIDE-20092, JBIDE-20361, https://bugs.eclipse.org/bugs/show_bug.cgi?id=471717 > We now should centralize the code that creates those StyledTexts -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:34:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Wed, 14 Oct 2015 15:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118411#comment-13118411 ] Len DiMaggio commented on JBTIS-520: ------------------------------------ OK - Now, I see the same thing that Paul sees. Very good! > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.Alpha2, 9.0.0.GA > > Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, ea.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20935: -------------------------------------- Assignee: Konstantin Marmalyukov Assigning to Konstantin hopping he can investigate it. [~fbricon] feel free to reassign if needed ;-) > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Labels: ui-scaling > Fix For: 4.3.x, 4.4.x > > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, screenshot-1.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:49:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:49:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20935: ----------------------------------- Fix Version/s: 4.3.x 4.4.x > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Labels: ui-scaling > Fix For: 4.3.x, 4.4.x > > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, screenshot-1.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 14 Oct 2015 15:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20368) Icons in Batch flow editor are partially not visible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118420#comment-13118420 ] Alexey Kazakov commented on JBIDE-20368: ---------------------------------------- Thanks! > Icons in Batch flow editor are partially not visible > ---------------------------------------------------- > > Key: JBIDE-20368 > URL: https://issues.jboss.org/browse/JBIDE-20368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Affects Versions: 4.3.0.Beta2 > Environment: Linux, GTK3 or GTK2 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.3.x > > Attachments: BatchGTK2.png, BatchGTK3.png > > > Icons (Zoom in/out/actual, save as image, print) are partially hidden. See screenshots. > I'm on Linux (Fedora 22). I've tried both GTK3 (3.16.5) and GTK2 (2.24.28). > GTK3: > !BatchGTK3.png! > GTK2: > !BatchGTK2.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 15:56:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Wed, 14 Oct 2015 15:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20927) Validation framework errors in tests on jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin reassigned JBIDE-20927: ------------------------------------- Assignee: Denis Golovin (was: Viacheslav Kabanovich) > Validation framework errors in tests on jenkins > ----------------------------------------------- > > Key: JBIDE-20927 > URL: https://issues.jboss.org/browse/JBIDE-20927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > {code}!ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.191 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.194 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist. > !ENTRY org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.203 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist. > at org.eclipse.wst.validation.internal.ValidatorExtensionReader.process(ValidatorExtensionReader.java:86) > at org.eclipse.wst.validation.internal.ExtensionValidators.(ExtensionValidators.java:43) > at org.eclipse.wst.validation.internal.ExtensionValidators.instance(ExtensionValidators.java:36) > at org.eclipse.wst.validation.internal.ValManager.getV2Validators(ValManager.java:345) > at org.eclipse.wst.validation.internal.ValManager.getValidatorsNotCached(ValManager.java:221) > at org.eclipse.wst.validation.internal.ValManager.access$1(ValManager.java:220) > at org.eclipse.wst.validation.internal.ValManager$ValidatorCache.getValidatorsCached(ValManager.java:1256) > at org.eclipse.wst.validation.internal.ValManager.getValidators(ValManager.java:197) > at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:745) > at org.eclipse.wst.validation.internal.ValBuilderJob.startingValidation(ValBuilderJob.java:148) > at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:122) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 1 org.eclipse.wst.validation 4 0 2015-10-08 16:03:40.205 > !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:04:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118424#comment-13118424 ] Jeff Cantrill commented on JBIDE-20601: --------------------------------------- [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service Current implementation produces the former which is what we desire. What more do we need provide? It seems to me we should allow a user to modify the exposed port which should be addressed in JBIDE-20531. We may need additional prompts and texts to clarify what this page allows you to configure. User's may wish to have additional routes, but I think that should be a follow-on action; this flow is supposed to be the fastest path to deploying an image. We should consider closing this issue or modifying it to reflect the need for additional verbiage for the user. > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:05:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118424#comment-13118424 ] Jeff Cantrill edited comment on JBIDE-20601 at 10/14/15 4:04 PM: ----------------------------------------------------------------- [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service Current implementation produces the former which is what we desire. What more do we need to provide? It seems to me we should allow a user to modify the exposed port which should be addressed in JBIDE-20531. We may need additional prompts and texts to clarify what this page allows you to configure. User's may wish to have additional routes, but I think that should be a follow-on action; this flow is supposed to be the fastest path to deploying an image. We should consider closing this issue or modifying it to reflect the need for additional verbiage for the user. was (Author: jcantrill): [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service Current implementation produces the former which is what we desire. What more do we need provide? It seems to me we should allow a user to modify the exposed port which should be addressed in JBIDE-20531. We may need additional prompts and texts to clarify what this page allows you to configure. User's may wish to have additional routes, but I think that should be a follow-on action; this flow is supposed to be the fastest path to deploying an image. We should consider closing this issue or modifying it to reflect the need for additional verbiage for the user. > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:54:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20714) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118435#comment-13118435 ] Jeff Cantrill commented on JBIDE-20714: --------------------------------------- [~fbricon] fixed. made pr against 4.3.x > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20714 > URL: https://issues.jboss.org/browse/JBIDE-20714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker, merge_into_master > Fix For: 4.3.1.Beta1 > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:54:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20714) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20714: ---------------------------------- Labels: docker merge_into_master (was: docker) > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20714 > URL: https://issues.jboss.org/browse/JBIDE-20714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker, merge_into_master > Fix For: 4.3.1.Beta1 > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:56:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 14 Oct 2015 16:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118436#comment-13118436 ] Rob Stryker commented on JBIDE-20071: ------------------------------------- [~giannitom] Is this replicatable without JBoss Tools? It seems to me like an issue with the JBoss implementation, and not an issue with JBT? > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:56:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20597: ---------------------------------- Summary: Add connection management to deploy image wizard (was: deploy to openshift wont let me create an openshift connection nor project) > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:56:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20597: ---------------------------------- Issue Type: Enhancement (was: Bug) > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:57:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118437#comment-13118437 ] Jeff Cantrill commented on JBIDE-20597: --------------------------------------- Modified title since portion is covered in JBIDE-20721 > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 16:58:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 16:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118438#comment-13118438 ] Jeff Cantrill commented on JBIDE-20596: --------------------------------------- [~mlabuda] [~fbricon] anyway to know if this has been corrected in JBDS? Could it just be the cut of the build missed this fix? > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 17:04:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 17:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20946) Add multi-tag filtering to templates In-Reply-To: References: Message-ID: Jeff Cantrill created JBIDE-20946: ------------------------------------- Summary: Add multi-tag filtering to templates Key: JBIDE-20946 URL: https://issues.jboss.org/browse/JBIDE-20946 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Final Reporter: Jeff Cantrill Priority: Optional Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 17:07:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 14 Oct 2015 17:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20542) Allow a user to add environment variables in deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20542: ---------------------------------- Description: Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. > Allow a user to add environment variables in deploy image wizard > ---------------------------------------------------------------- > > Key: JBIDE-20542 > URL: https://issues.jboss.org/browse/JBIDE-20542 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 18:39:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 14 Oct 2015 18:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20739) Cannot delete last number in number fields of JVM Monitor Preference Page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker updated JBIDE-20739: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Cannot delete last number in number fields of JVM Monitor Preference Page > ------------------------------------------------------------------------- > > Key: JBIDE-20739 > URL: https://issues.jboss.org/browse/JBIDE-20739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jmx > Affects Versions: 4.3.0.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: search-timeout-editing.mp4 > > > All number fields don't allow to delete last number. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 18:41:01 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 14 Oct 2015 18:41:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20581) Wrong names used for servers added via runtime detection (WFLY10, EAP7) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker updated JBIDE-20581: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Wrong names used for servers added via runtime detection (WFLY10, EAP7) > ----------------------------------------------------------------------- > > Key: JBIDE-20581 > URL: https://issues.jboss.org/browse/JBIDE-20581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.CR1 > Environment: Nightly JBDS from 6.9.2015. > org.jboss.tools.runtime.core.feature (3.1.0.CR1-v20150905-0435-B808) > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > I tried to add WildFly 10 and EAP 7.0 servers via runtime detection and this is what i got: > * EAP 7.0 - Server name: "EAP 7.0" - shouldn't it be "JBoss EAP 7.0"? At least previous versions have "JBoss" in name ("JBoss EAP 6.4") > * WildFly 10 - Server name: "Wildfly 10.0". I think, that there should be capital F: "WildFly 10" > * WildFly 10 Servlet only distribution - Server name: "EAP-Web 10.0" - this seems completely wrong. > Btw. Does EAP 7 have servlet only distribution like WFLY9/10 has? I couldn't find any, but classes like `org.jboss.ide.eclipse.as.core.server.bean.ServerBeanTypeEAP70Web` suggest that there should be something somewhere ;-) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 01:06:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 15 Oct 2015 01:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118469#comment-13118469 ] Misha Ali commented on TOOLSDOC-610: ------------------------------------ PR is now merged. We should be able to close this issue now, if that is all it's waiting on. > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > Attachments: hmt_config_file_icon_modified.png, hmt_firstapp.adoc, hmt_icon_modified.png > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. > [~supriya.bharadwaj], also look at TOOLSDOC-646 and decide if we need to add info for emulator/skin change in the article. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 02:36:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 15 Oct 2015 02:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20596: ---------------------------------- Steps to Reproduce: ASSERT: There is no OpenShift connection. EXEC: Open New OpenShift Application wizard via JBoss Central EXEC: Select OpenShift 3 server type and OAuth authentication method. EXEC: Enter any token into a token field - it must be pasted, not typed. RESULT: Next button is disabled. EXPECTED RESULT: Next button is enabled Workaround Description: There are several ways to workaround this issues: a) Check and uncheck checkbox for a default server usage b) Switch to Basic authentication method and then switch to OAuth again - because token is cached, the Next button gets enabled. c) Instead of pasting token, paste it. Or remove last character and type it again, then the Next button gets enabled. Workaround: Workaround Exists > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 02:36:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 15 Oct 2015 02:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118476#comment-13118476 ] Mari?n Labuda commented on JBIDE-20596: --------------------------------------- [~jcantrill] yeah, issue still persists even in JBDS 9.0.0.CR2b build (GA). I added accurate steps to reproduce and also workarounds. > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 02:38:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 15 Oct 2015 02:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-688) JBDS 9.0: Maven Basics Article In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118477#comment-13118477 ] Misha Ali commented on TOOLSDOC-688: ------------------------------------ https://access.redhat.com/articles/1521433 Created and published. > JBDS 9.0: Maven Basics Article > ------------------------------ > > Key: TOOLSDOC-688 > URL: https://issues.jboss.org/browse/TOOLSDOC-688 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > This issue tracks the creation of the Maven Basics article for JBDS 9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 02:38:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 15 Oct 2015 02:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-688) JBDS 9.0: Maven Basics Article In-Reply-To: References: Message-ID: Misha Ali created TOOLSDOC-688: ---------------------------------- Summary: JBDS 9.0: Maven Basics Article Key: TOOLSDOC-688 URL: https://issues.jboss.org/browse/TOOLSDOC-688 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Components: General documentation issues Affects Versions: 4.3.0.Final Reporter: Misha Ali Assignee: Misha Ali Fix For: 4.3.0.Final This issue tracks the creation of the Maven Basics article for JBDS 9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 02:42:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 15 Oct 2015 02:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-688) JBDS 9.0: Maven Basics Article In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali closed TOOLSDOC-688. ------------------------------ Resolution: Done Labels: Maven (was: ) > JBDS 9.0: Maven Basics Article > ------------------------------ > > Key: TOOLSDOC-688 > URL: https://issues.jboss.org/browse/TOOLSDOC-688 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Maven > Fix For: 4.3.0.Final > > > This issue tracks the creation of the Maven Basics article for JBDS 9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 03:46:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 15 Oct 2015 03:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118490#comment-13118490 ] Max Rydahl Andersen commented on JBTIS-520: ------------------------------------------- Awesome - I hope you all agree this approach of not mixing streams and exposing more and more sites is simpler for GA's (at least for the enduser and our sanity) > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.Alpha2, 9.0.0.GA > > Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, ea.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 03:52:01 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 15 Oct 2015 03:52:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118490#comment-13118490 ] Max Rydahl Andersen edited comment on JBTIS-520 at 10/15/15 3:51 AM: --------------------------------------------------------------------- Awesome - I hope you all agree this approach of not mixing streams and not exposing more and more sites is simpler for GA's (at least for the enduser and our sanity) was (Author: maxandersen): Awesome - I hope you all agree this approach of not mixing streams and exposing more and more sites is simpler for GA's (at least for the enduser and our sanity) > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.Alpha2, 9.0.0.GA > > Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, ea.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:24:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 15 Oct 2015 05:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118530#comment-13118530 ] Max Rydahl Andersen commented on JBIDE-19178: --------------------------------------------- [~jcantrill] it is probably not very diferent, but I dont consider this for explorer view currently - this view was more for the server view where I do run as/debug as etc. works. If it can also be in explorer view great, but the UI interaction for that is different (no runs as for example) > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:25:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 15 Oct 2015 05:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118530#comment-13118530 ] Max Rydahl Andersen edited comment on JBIDE-19178 at 10/15/15 5:24 AM: ----------------------------------------------------------------------- [~jcantrill] it is probably not very diferent, but I dont consider this for explorer view currently - this view was more for the server view where I do run as/debug as etc. works. If it can also be in explorer view great, but the UI interaction for that is different (i.e. openshift explorer does not know what eclipse project/module is deployed to it) was (Author: maxandersen): [~jcantrill] it is probably not very diferent, but I dont consider this for explorer view currently - this view was more for the server view where I do run as/debug as etc. works. If it can also be in explorer view great, but the UI interaction for that is different (no runs as for example) > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:58:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 15 Oct 2015 05:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118542#comment-13118542 ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- [~akazakov] Here is what the proposed PR implements: https://vid.me/pkel > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 07:07:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 15 Oct 2015 07:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118568#comment-13118568 ] Max Rydahl Andersen commented on JBIDE-19178: --------------------------------------------- btw. about using the properties view, I think that is fine to offload details. We can still have interesting events (like ongoing builds, status of the pods etc.) show up as nodes or labels directly in the tree. > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 07:21:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 15 Oct 2015 07:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118574#comment-13118574 ] Max Rydahl Andersen commented on JBIDE-20071: --------------------------------------------- [~rob.stryker] even if it is an issue of EAP then it affects tools since we now always explode the jars to WEB-INF/lib with no option for the user to turn it off - so if that is true JBIDE-20577 become that more important. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 08:00:03 2015 From: issues at jboss.org (Giovanni Tomasicchio (JIRA)) Date: Thu, 15 Oct 2015 08:00:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118591#comment-13118591 ] Giovanni Tomasicchio commented on JBIDE-20071: ---------------------------------------------- [~maxandersen] I agree. I can't upgrade Eclipse to Mars because of this issue. [~rob.stryker] I'm not sure if this is a JBoss bug because specs refers to a "JAR file inside WEB-INF/lib". Maybe JBoss developers have enabled this feature only for compressed JAR. I wonder if this problem also occurs with Wildfly. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 08:13:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Thu, 15 Oct 2015 08:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118596#comment-13118596 ] Supriya Bharadwaj commented on TOOLSDOC-307: -------------------------------------------- Unable to import the app (JBoss EAP 6) into JBDS (9.0GA) Documented the steps that I have done so far and the errors at: https://docs.google.com/document/d/19J_RDjHIIo_gtZrPKw87Kqgld3bMfFjHpVDpcrrAJIk/edit# IRC chat with Marian to solve this >> asked to delete local maven repo > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 08:14:00 2015 From: issues at jboss.org (Vsevolod Golovanov (JIRA)) Date: Thu, 15 Oct 2015 08:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118597#comment-13118597 ] Vsevolod Golovanov commented on JBIDE-20071: -------------------------------------------- [~giannitom], no, it doesn't occur with Wildfly, that's part of the premise of this task. I have a webapplication running right now with resources and classes in lib jars (see above comments). As far as I know, Java EE specs don't say anything about exploded deployments at all. If you bring the spec into the question, then exploded ears, wars and ejbs may justifiably not work for the same reason as jars in war libs. So it is a JBoss AS bug. If there is a bug. Can you attach the sample project? It was already implemented in this task, that this explodiness is enabled only for selected server versions which are known to support it. So if there is a bug, the server version support should be amended. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 09:23:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Thu, 15 Oct 2015 09:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-518) Publish JBTIS 4.3.0.Alpha2/ JBDSIS 9.0.0.Alpha2 to jbosstools website In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu closed JBTIS-518. ---------------------------- Resolution: Done rebased and merged > Publish JBTIS 4.3.0.Alpha2/ JBDSIS 9.0.0.Alpha2 to jbosstools website > --------------------------------------------------------------------- > > Key: JBTIS-518 > URL: https://issues.jboss.org/browse/JBTIS-518 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Paul Leacu > Assignee: Paul Leacu > > Publish JBTIS 4.3.0.Alpha2/ JBDSIS 9.0.0.Alpha2 to jbosstools website -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 09:58:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 15 Oct 2015 09:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18911) allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda reassigned JBIDE-18911: ------------------------------------- Assignee: (was: Mari?n Labuda) > allow URL in the form "from-code=git at github.com" for custom app source code and downloadable cartridges > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18911 > URL: https://issues.jboss.org/browse/JBIDE-18911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Labels: application_wizard, embed_wizard, new_and_noteworthy > Fix For: 4.2.x > > Attachments: clone-error.png, source-code.png > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges > The exact form is documented in the github (and general purpose git-) documentation: https://gist.github.com/grawity/4392747 > {quote} > SSH, aka git at github.com: or ssh://git at github.com/ > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 09:59:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 15 Oct 2015 09:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18911) allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-18911: ---------------------------------- Fix Version/s: 4.4.x (was: 4.2.x) > allow URL in the form "from-code=git at github.com" for custom app source code and downloadable cartridges > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18911 > URL: https://issues.jboss.org/browse/JBIDE-18911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Labels: application_wizard, embed_wizard, new_and_noteworthy > Fix For: 4.4.x > > Attachments: clone-error.png, source-code.png > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges > The exact form is documented in the github (and general purpose git-) documentation: https://gist.github.com/grawity/4392747 > {quote} > SSH, aka git at github.com: or ssh://git at github.com/ > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 09:59:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 15 Oct 2015 09:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18911) allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda reassigned JBIDE-18911: ------------------------------------- Assignee: Mari?n Labuda > allow URL in the form "from-code=git at github.com" for custom app source code and downloadable cartridges > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18911 > URL: https://issues.jboss.org/browse/JBIDE-18911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Mari?n Labuda > Labels: application_wizard, embed_wizard, new_and_noteworthy > Fix For: 4.4.x > > Attachments: clone-error.png, source-code.png > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges > The exact form is documented in the github (and general purpose git-) documentation: https://gist.github.com/grawity/4392747 > {quote} > SSH, aka git at github.com: or ssh://git at github.com/ > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 10:13:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 10:13:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118679#comment-13118679 ] Nick Boldt commented on JBIDE-20609: ------------------------------------ +1, I like this new workflow. Only thing I'm not 100% behind is the text label "Manage Early Access"... but I can't think of a better way to explain that it's a link to show what EA content is installed and to optionally disable the EA URL to prevent getting updates. "Manage" seems the best option. (And I'm glad you didn't label it "Early-Access", with a hyphen.) :D Curious: if I disable the EA URL as you did in the video, and I then try to install Arquillian, will I once again be prompted to accept the EA rules, which will result in the EA URL being re-enabled? Or does my explicitly having disabled it cause a NEW dialog to pop up saying "sorry, you disabled EA. Can't update this until you explicitly re-enable EA again." ? > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 10:28:00 2015 From: issues at jboss.org (Klemen Ferjancic (JIRA)) Date: Thu, 15 Oct 2015 10:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118719#comment-13118719 ] Klemen Ferjancic commented on JBDS-3538: ---------------------------------------- Using Eclipse Mars.1 on OpenSUSE, can't install JBOSS Tools An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Error closing the output stream for osgi.bundle,ternjs,1.0.0.201508302102 on repository file:/home/cen/liis/ide/eclipse/. Error unzipping /tmp/ternjs_1.0.0.2015083021021115708151814408218.jar: Unexpected end of ZLIB input stream > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 10:29:01 2015 From: issues at jboss.org (Klemen Ferjancic (JIRA)) Date: Thu, 15 Oct 2015 10:29:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118719#comment-13118719 ] Klemen Ferjancic edited comment on JBDS-3538 at 10/15/15 10:28 AM: ------------------------------------------------------------------- Using Eclipse Mars.1 on OpenSUSE, can't install JBOSS Tools An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Error closing the output stream for osgi.bundle,ternjs,1.0.0.201508302102 on repository file:/home/redacted/ide/eclipse/. Error unzipping /tmp/ternjs_1.0.0.2015083021021115708151814408218.jar: Unexpected end of ZLIB input stream was (Author: cen): Using Eclipse Mars.1 on OpenSUSE, can't install JBOSS Tools An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Error closing the output stream for osgi.bundle,ternjs,1.0.0.201508302102 on repository file:/home/cen/liis/ide/eclipse/. Error unzipping /tmp/ternjs_1.0.0.2015083021021115708151814408218.jar: Unexpected end of ZLIB input stream > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 10:38:02 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 15 Oct 2015 10:38:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118724#comment-13118724 ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- {quote}if I disable the EA URL as you did in the video, and I then try to install Arquillian, will I once again be prompted to accept the EA rules, which will result in the EA URL being re-enabled?{quote} Yes. Accepting Early Access is somehow equivalent to adding the URL. (there's also a preference that is set, but it's an underlying implementation detail). > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 10:41:01 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Thu, 15 Oct 2015 10:41:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118727#comment-13118727 ] Mickael Istria commented on JBDS-3538: -------------------------------------- Hi [~cen], thanks a lot for the report. Can you please give more details about: * Where you using Marketplace client or installing from the update-site? * If update-site, can you please confirm the URL you used? * Did that just happened a dozen of minutes ago? * Can you please tell us your IP? * Did it happen only once or is it something you get systematically ? Sorry for being so curious, but we have much trouble to find a way to reproduce or understand those issues, so we take every hint we can imagine ;) > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 10:45:02 2015 From: issues at jboss.org (Giovanni Tomasicchio (JIRA)) Date: Thu, 15 Oct 2015 10:45:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118729#comment-13118729 ] Giovanni Tomasicchio commented on JBIDE-20071: ---------------------------------------------- Sorry, my fault. Trying to reproduce the issue in a simple web project I found that the "file not found" exception occurs for a template.tag file placed in META-INF\tags of an exploded JAR in WEB-INF\lib of a WAR. The template.tag file is declared in a META-INF\template.tld that contains the following lines: template /META-INF/tags/template.tag So JBoss is not able to access the path /META-INF/tags/template.tag if the JAR is exploded. I verified this issue simply by exploding the JAR that contains the .tag file. Sorry again for the wrong reporting. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:00:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 15 Oct 2015 11:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20766) Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-20766. --------------------------------- Resolution: Done 4.3.1.x branch was merged into 4.3.x. Resolving > Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch > ------------------------------------------------------------- > > Key: JBIDE-20766 > URL: https://issues.jboss.org/browse/JBIDE-20766 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > For jbosstools-openshift, ongoing work towards the JBoss Tools 4.3.1.Final release must happen on the jbosstools-4.3.1.x branch. > Once 4.3.0.Final has been released, the jbosstools-4.3.1.x branch must be merged into jbosstools-4.3.x branch, where subsequent commits will be pushed, until the 4.3.1.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:02:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3545) For JBDS 9.0.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: Nick Boldt created JBDS-3545: -------------------------------- Summary: For JBDS 9.0.1.Beta1: Prepare for future Beta1 Key: JBDS-3545 URL: https://issues.jboss.org/browse/JBDS-3545 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 9.0.1.Beta1 For JBDS 9.0.1.Beta1: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:02:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:02:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20947: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 Key: JBIDE-20947 URL: https://issues.jboss.org/browse/JBIDE-20947 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Nick Boldt Priority: Blocker Fix For: 4.3.1.Beta1 For JBIDE 4.3.1.Beta1: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:02:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:02:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20948: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] Key: JBIDE-20948 URL: https://issues.jboss.org/browse/JBIDE-20948 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid, cordovasim Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Aerogear]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22aerogear-hybrid%22%2C%22cordovasim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:02:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:02:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20949) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central Discovery] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20949: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central Discovery] Key: JBIDE-20949 URL: https://issues.jboss.org/browse/JBIDE-20949 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: discovery Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Central Discovery]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22discovery%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:02:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:02:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20950) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [VPE] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20950: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [VPE] Key: JBIDE-20950 URL: https://issues.jboss.org/browse/JBIDE-20950 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: visual-page-editor-core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [VPE]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22visual-page-editor-core%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:02:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:02:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20951: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] Key: JBIDE-20951 URL: https://issues.jboss.org/browse/JBIDE-20951 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: qa Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:02:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:02:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20952) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20952: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] Key: JBIDE-20952 URL: https://issues.jboss.org/browse/JBIDE-20952 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22build%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3545) For JBDS 9.0.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBDS-3545: -------------------------------- Assignee: Nick Boldt > For JBDS 9.0.1.Beta1: Prepare for future Beta1 > ---------------------------------------------- > > Key: JBDS-3545 > URL: https://issues.jboss.org/browse/JBDS-3545 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 9.0.1.Beta1 > > > For JBDS 9.0.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20953) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20953: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] Key: JBIDE-20953 URL: https://issues.jboss.org/browse/JBIDE-20953 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Server]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22server%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:05 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:05 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20954) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Hibernate] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20954: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Hibernate] Key: JBIDE-20954 URL: https://issues.jboss.org/browse/JBIDE-20954 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: hibernate Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Hibernate]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22hibernate%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:06 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20955) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Base] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20955: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Base] Key: JBIDE-20955 URL: https://issues.jboss.org/browse/JBIDE-20955 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: usage, common/jst/core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Base]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22usage%22%2C%22common%2Fjst%2Fcore%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:06 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20956) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [OpenShift] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20956: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [OpenShift] Key: JBIDE-20956 URL: https://issues.jboss.org/browse/JBIDE-20956 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [OpenShift]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22openshift%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:06 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20957: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] Key: JBIDE-20957 URL: https://issues.jboss.org/browse/JBIDE-20957 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: playground Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Playground]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22playground%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:06 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20959) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JST] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20959: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JST] Key: JBIDE-20959 URL: https://issues.jboss.org/browse/JBIDE-20959 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: common/jst/core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [JST]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22common%2Fjst%2Fcore%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:06 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20958) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JavaEE] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20958: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JavaEE] Key: JBIDE-20958 URL: https://issues.jboss.org/browse/JBIDE-20958 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: seam2, cdi, cdi-extensions, jsf Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [JavaEE]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22seam2%22%2C%22jsf%22%2C%22cdi%22%2C%22cdi-extensions%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:06 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20960: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] Key: JBIDE-20960 URL: https://issues.jboss.org/browse/JBIDE-20960 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: forge Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Forge]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:03:06 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:03:06 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20961) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Birt] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20961: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Birt] Key: JBIDE-20961 URL: https://issues.jboss.org/browse/JBIDE-20961 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: birt Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Birt]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22birt%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20962) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [BrowserSim] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20962: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [BrowserSim] Key: JBIDE-20962 URL: https://issues.jboss.org/browse/JBIDE-20962 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: browsersim Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [BrowserSim]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22browsersim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20963) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20963: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] Key: JBIDE-20963 URL: https://issues.jboss.org/browse/JBIDE-20963 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: webservices Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Webservices]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22webservices%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20964) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Arquillian] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20964: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Arquillian] Key: JBIDE-20964 URL: https://issues.jboss.org/browse/JBIDE-20964 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: arquillian Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Arquillian]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22arquillian%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20965) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Freemarker] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20965: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Freemarker] Key: JBIDE-20965 URL: https://issues.jboss.org/browse/JBIDE-20965 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: freemarker Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [Freemarker]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22freemarker%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20966) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20966: ---------------------------------- Summary: 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: maven, project-examples, central Reporter: Nick Boldt Priority: Blocker 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22maven%22%2C%22central%22%2C%22project-examples%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20967) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20967: ---------------------------------- Summary: For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] Key: JBIDE-20967 URL: https://issues.jboss.org/browse/JBIDE-20967 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: livereload Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.1.Beta1 [LiveReload]: 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} org.jboss.tools parent 4.3.1.Beta1-SNAPSHOT {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22livereload%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:13:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 15 Oct 2015 11:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20968) ds_my_next_master_unresolved and ds_my_next_maint_unresolved are empty In-Reply-To: References: Message-ID: Rob Stryker created JBIDE-20968: ----------------------------------- Summary: ds_my_next_master_unresolved and ds_my_next_maint_unresolved are empty Key: JBIDE-20968 URL: https://issues.jboss.org/browse/JBIDE-20968 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Rob Stryker See topic. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:13:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 15 Oct 2015 11:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20968) ds_my_next_master_unresolved and ds_my_next_maint_unresolved are empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker reassigned JBIDE-20968: ----------------------------------- Assignee: Max Rydahl Andersen > ds_my_next_master_unresolved and ds_my_next_maint_unresolved are empty > ---------------------------------------------------------------------- > > Key: JBIDE-20968 > URL: https://issues.jboss.org/browse/JBIDE-20968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > > See topic. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:14:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 15 Oct 2015 11:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20968) ds_my_next_master_unresolved and ds_my_next_maint_unresolved are empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker updated JBIDE-20968: -------------------------------- Labels: processwork (was: ) > ds_my_next_master_unresolved and ds_my_next_maint_unresolved are empty > ---------------------------------------------------------------------- > > Key: JBIDE-20968 > URL: https://issues.jboss.org/browse/JBIDE-20968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Labels: processwork > > See topic. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:15:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 15 Oct 2015 11:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20964) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Arquillian] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco reassigned JBIDE-20964: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Arquillian] > ------------------------------------------------------------ > > Key: JBIDE-20964 > URL: https://issues.jboss.org/browse/JBIDE-20964 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Arquillian]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22arquillian%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:15:01 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 15 Oct 2015 11:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20961) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Birt] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco reassigned JBIDE-20961: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Birt] > ------------------------------------------------------ > > Key: JBIDE-20961 > URL: https://issues.jboss.org/browse/JBIDE-20961 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Birt]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22birt%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:22:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 11:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118750#comment-13118750 ] Nick Boldt commented on JBIDE-20609: ------------------------------------ +1, seems legit. I'd recommend this for inclusion in 4.3.1 and 4.4.0. Do the other stakeholders agree? [~mmusaji] [~mhusnain] [~crobson] [~akazakov] [~maxandersen] [~jpallich] [~burrsutter] [~fbricon] > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 11:32:00 2015 From: issues at jboss.org (Mustafa Musaji (JIRA)) Date: Thu, 15 Oct 2015 11:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118758#comment-13118758 ] Mustafa Musaji commented on JBIDE-20609: ---------------------------------------- +1 after reviewing the video, nice addition and cleans things up. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:00:01 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 15 Oct 2015 12:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20964) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Arquillian] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco closed JBIDE-20964. --------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Arquillian] > ------------------------------------------------------------ > > Key: JBIDE-20964 > URL: https://issues.jboss.org/browse/JBIDE-20964 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Arquillian]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22arquillian%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:08:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 15 Oct 2015 12:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20961) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Birt] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco closed JBIDE-20961. --------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Birt] > ------------------------------------------------------ > > Key: JBIDE-20961 > URL: https://issues.jboss.org/browse/JBIDE-20961 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Birt]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22birt%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:21:00 2015 From: issues at jboss.org (Klemen Ferjancic (JIRA)) Date: Thu, 15 Oct 2015 12:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118772#comment-13118772 ] Klemen Ferjancic commented on JBDS-3538: ---------------------------------------- 1. Marketplace client 2. / 3. Yes, a few min before I commented 4. I left my workplace so I dont have IP right now 5. Based on recent comments the bug must have happened just a few days ago. Used to install Jboss tools without problem several times during the summer. Just retried at home as of time of this writing, ip 84.52.146.42, same error. > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:22:00 2015 From: issues at jboss.org (Klemen Ferjancic (JIRA)) Date: Thu, 15 Oct 2015 12:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118772#comment-13118772 ] Klemen Ferjancic edited comment on JBDS-3538 at 10/15/15 12:21 PM: ------------------------------------------------------------------- 1. Marketplace client 2. / 3. Yes, a few min before I commented 4. I left my workplace so I dont have IP right now 5. Based on recent comments the bug must have happened just a few days ago. Used to install Jboss tools without problem several times during the summer. But as of today it failed every single time I tried it. Just retried at home as of time of this writing, ip 84.52.146.42, same error. was (Author: cen): 1. Marketplace client 2. / 3. Yes, a few min before I commented 4. I left my workplace so I dont have IP right now 5. Based on recent comments the bug must have happened just a few days ago. Used to install Jboss tools without problem several times during the summer. Just retried at home as of time of this writing, ip 84.52.146.42, same error. > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:46:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 15 Oct 2015 12:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1609) Installer should check system prerequisites and warn user if they are not fullfilled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-1609: -------------------------------- > Installer should check system prerequisites and warn user if they are not fullfilled > ------------------------------------------------------------------------------------ > > Key: JBDS-1609 > URL: https://issues.jboss.org/browse/JBDS-1609 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Minor > Fix For: 9.x > > > To prevent insufficient machine parameters or setting installer should do basic check for some parameters like: > - memory amount > - maximum open file limit > - maximum thread count limit > - internet connection > - others reasonable criteria should be added here > If these criteria aren't met, installer should display add warning page before further installation saying that requirements aren't satisfied and tools may not work properly. Reason for this is that sometimes JBDS is used in very strict environment (typically training rooms, universities, etc where many system resources are limited or blocked) but user isn't warned and after install user can see after that lots of runtime errors and got bad feeling about the tool. This should be avoided and user should be at least warn that he is running JBDS in inappropriate environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:46:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 15 Oct 2015 12:46:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1504) allow users to create cases from JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-1504: -------------------------------- > allow users to create cases from JBDS > ------------------------------------- > > Key: JBDS-1504 > URL: https://issues.jboss.org/browse/JBDS-1504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: integration > Environment: All > Reporter: Andrew Hecox > Assignee: Max Rydahl Andersen > Fix For: 9.x, LATER > > > user-story: as a JBoss customer, I can create a case with support from JBDS so that I can easily get help solving the problem I'm working on in my editor > notes: I think something which allowed a user to create a problem description, as well as send any applicable files, would be a good value add to JBDS. We have a public, stable, API for this: > https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/ > we may deprecate some schema items in the next month or two, but otherwise it's locked in place for the next 7+ years. This functionality presumably would only be in the productized version, unless it was replaced with JIRA integration (or comparable) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:46:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 15 Oct 2015 12:46:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2625) Provide on-line installer launchable via JNLP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-2625: -------------------------------- > Provide on-line installer launchable via JNLP > --------------------------------------------- > > Key: JBDS-2625 > URL: https://issues.jboss.org/browse/JBDS-2625 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.x > > > Instead of always downloading offline installer and then run installation manually, would be good to have online version of installer that would let: > # start installer via JNLP > # select if EAP/WildFly should be installed too > (1) Should be easy to implement, because it requires only excluding update site bits from jar, provide URL for update site and create JNLP configuration; > (2) Requires EAP download integration into IzPack (would be good if IzPack has supported online installation itself) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 12:46:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Thu, 15 Oct 2015 12:46:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2065) Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-2065: -------------------------------- > Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE > ----------------------------------------------------------------------------------- > > Key: JBDS-2065 > URL: https://issues.jboss.org/browse/JBDS-2065 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 5.0.0.M5 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.x > > Attachments: Screen Shot 2012-03-09 at 10.05.17.jpg > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 13:14:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 13:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20955) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Base] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20955: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Base] > ------------------------------------------------------ > > Key: JBIDE-20955 > URL: https://issues.jboss.org/browse/JBIDE-20955 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Base]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22usage%22%2C%22common%2Fjst%2Fcore%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 13:39:05 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 15 Oct 2015 13:39:05 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20754) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker resolved JBIDE-20754. --------------------------------- Resolution: Duplicate Issue I'm closing this as duplicate. ProcessInformationStore is likely to be deleted in master > org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2 > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20754 > URL: https://issues.jboss.org/browse/JBIDE-20754 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Beta2 > Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.Beta1 > > > org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces. > In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows. > {noformat} > java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at java.lang.Runtime.exec(Runtime.java:450) > at java.lang.Runtime.exec(Runtime.java:347) > at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97) > at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) > at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.(ProcessImpl.java:386) > at java.lang.ProcessImpl.start(ProcessImpl.java:137) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 7 more > {noformat} > I'm note sure what the impact is - I don't necessarily notice anything not working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 13:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20955) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Base] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20955. ---------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Base] > ------------------------------------------------------ > > Key: JBIDE-20955 > URL: https://issues.jboss.org/browse/JBIDE-20955 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Base]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22usage%22%2C%22common%2Fjst%2Fcore%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 13:40:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 15 Oct 2015 13:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20729) Investigate ProcessInformationStore for its uses and whether it can be replaced In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker updated JBIDE-20729: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Investigate ProcessInformationStore for its uses and whether it can be replaced > ------------------------------------------------------------------------------- > > Key: JBIDE-20729 > URL: https://issues.jboss.org/browse/JBIDE-20729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > https://issues.jboss.org/browse/JBIDE-20510 was opened for a small bug regarding spaces on windows, but it revealed to me that the java8 I have installed there lacks a jps command. This means we need to revisit whether or not the ProcessInformationSotre is the proper solution for what it is doing, or if we can replace it with the debug code in jbt-base. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 13:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20959) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JST] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20959: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JST] > ----------------------------------------------------- > > Key: JBIDE-20959 > URL: https://issues.jboss.org/browse/JBIDE-20959 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [JST]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22common%2Fjst%2Fcore%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 13:41:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 15 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20729) Investigate ProcessInformationStore for its uses and whether it can be replaced In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118804#comment-13118804 ] Rob Stryker commented on JBIDE-20729: ------------------------------------- Class can be removed, but not in maintenance. Class is currently API and cannot be removed since Fuse depends on it. > Investigate ProcessInformationStore for its uses and whether it can be replaced > ------------------------------------------------------------------------------- > > Key: JBIDE-20729 > URL: https://issues.jboss.org/browse/JBIDE-20729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > https://issues.jboss.org/browse/JBIDE-20510 was opened for a small bug regarding spaces on windows, but it revealed to me that the java8 I have installed there lacks a jps command. This means we need to revisit whether or not the ProcessInformationSotre is the proper solution for what it is doing, or if we can replace it with the debug code in jbt-base. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 13:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 13:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20959) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JST] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20959. ---------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JST] > ----------------------------------------------------- > > Key: JBIDE-20959 > URL: https://issues.jboss.org/browse/JBIDE-20959 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [JST]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22common%2Fjst%2Fcore%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 14:56:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 14:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20714) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118831#comment-13118831 ] Jeff Cantrill commented on JBIDE-20714: --------------------------------------- cherry-picked into master by [~fbricon] https://github.com/jbosstools/jbosstools-openshift/commit/6bacf87e41783249f97e71e99954457785483789 > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20714 > URL: https://issues.jboss.org/browse/JBIDE-20714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker > Fix For: 4.3.x > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 14:56:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 14:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20714) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20714: ---------------------------------- Labels: docker (was: docker merge_into_master) > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20714 > URL: https://issues.jboss.org/browse/JBIDE-20714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker > Fix For: 4.3.x > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:02:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 15:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill reassigned JBIDE-20531: ------------------------------------- Assignee: Jeff Cantrill > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-20531 > URL: https://issues.jboss.org/browse/JBIDE-20531 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add ports to a deployment other then just those exposed on the docker image -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:07:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 15:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20531: ---------------------------------- Description: Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image (was: Allow a user to add ports to a deployment other then just those exposed on the docker image) > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-20531 > URL: https://issues.jboss.org/browse/JBIDE-20531 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:12:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 15:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20531: ---------------------------------- Description: Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image * Also only remove those which were added * Only reset those which are defaults * Edit via double click was:Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-20531 > URL: https://issues.jboss.org/browse/JBIDE-20531 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:25:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 15 Oct 2015 15:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20969) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: Fred Bricon created JBIDE-20969: ----------------------------------- Summary: NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files Key: JBIDE-20969 URL: https://issues.jboss.org/browse/JBIDE-20969 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.3.0.Final Reporter: Fred Bricon Attachments: broken-hyperlink.xml If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log {noformat} ava.lang.NullPointerException at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) 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:1499) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) 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) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:26:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 15 Oct 2015 15:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20969) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20969: ----------------------------------- Assignee: Viacheslav Kabanovich > NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files > ------------------------------------------------------------------------------------- > > Key: JBIDE-20969 > URL: https://issues.jboss.org/browse/JBIDE-20969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Beta1 > > Attachments: broken-hyperlink.xml > > > If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log > {noformat} > ava.lang.NullPointerException > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) > at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:26:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 15 Oct 2015 15:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20969) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20969: -------------------------------- Fix Version/s: 4.3.1.Beta1 > NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files > ------------------------------------------------------------------------------------- > > Key: JBIDE-20969 > URL: https://issues.jboss.org/browse/JBIDE-20969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Beta1 > > Attachments: broken-hyperlink.xml > > > If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log > {noformat} > ava.lang.NullPointerException > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) > at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 15:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20969) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20969: -------------------------------------- Assignee: Daniel Azarov (was: Viacheslav Kabanovich) > NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files > ------------------------------------------------------------------------------------- > > Key: JBIDE-20969 > URL: https://issues.jboss.org/browse/JBIDE-20969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Daniel Azarov > Fix For: 4.3.1.Beta1 > > Attachments: broken-hyperlink.xml > > > If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log > {noformat} > ava.lang.NullPointerException > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) > at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 15:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 15:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20958) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JavaEE] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20958. ---------------------------------- Assignee: Alexey Kazakov Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [JavaEE] > -------------------------------------------------------- > > Key: JBIDE-20958 > URL: https://issues.jboss.org/browse/JBIDE-20958 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [JavaEE]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22seam2%22%2C%22jsf%22%2C%22cdi%22%2C%22cdi-extensions%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:13:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 15 Oct 2015 16:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20970) Upgrade Forge Runtime to 2.20.0.Final In-Reply-To: References: Message-ID: George Gastaldi created JBIDE-20970: --------------------------------------- Summary: Upgrade Forge Runtime to 2.20.0.Final Key: JBIDE-20970 URL: https://issues.jboss.org/browse/JBIDE-20970 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.3.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.3.1.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:15:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 15 Oct 2015 16:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20970) Upgrade Forge Runtime to 2.20.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi resolved JBIDE-20970. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 2.20.0.Final > ------------------------------------- > > Key: JBIDE-20970 > URL: https://issues.jboss.org/browse/JBIDE-20970 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 16:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20960: -------------------------------------- Assignee: George Gastaldi > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] > ------------------------------------------------------- > > Key: JBIDE-20960 > URL: https://issues.jboss.org/browse/JBIDE-20960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Forge]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:26:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 16:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20970) Upgrade Forge Runtime to 2.20.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20970: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Upgrade Forge Runtime to 2.20.0.Final > ------------------------------------- > > Key: JBIDE-20970 > URL: https://issues.jboss.org/browse/JBIDE-20970 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:39:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 15 Oct 2015 16:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118876#comment-13118876 ] Nick Boldt commented on JBIDE-20960: ------------------------------------ {quote} (2015-10-15 16:26:26) gastaldi: nickboldt, for JBIDE-20960 issues, it would be nice to have the "Due Date" also set (2015-10-15 16:26:33) jbossbot: jira [JBIDE-20960] For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] [Open (Unresolved) Sub-task, Blocker, George Gastaldi] https://issues.jboss.org/browse/JBIDE-20960 (2015-10-15 16:26:49) gastaldi: so we can know for how long we can postpone it :) (2015-10-15 16:27:15) gastaldi: jk, this is useful so we can prioritize over other issues (2015-10-15 16:27:59) gastaldi left the room (quit: Client Quit).{quote} So far I see no commits in https://github.com/jbosstools/jbosstools-forge/commits/jbosstools-4.3.x so there's no urgency to apply the PR, unless you KNOW you plan to do work in 4.3.x branch. If you have maintenance plans &/or outstanding bugs to fix, then the due date is ASAP so that your builds in 4.3.x are using the correct version of parent pom and are correctly upversioned. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] > ------------------------------------------------------- > > Key: JBIDE-20960 > URL: https://issues.jboss.org/browse/JBIDE-20960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Forge]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:45:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 16:45:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118877#comment-13118877 ] Alexey Kazakov commented on JBIDE-20960: ---------------------------------------- The Due Date is ASAP if you want to update forge in 4.3.1 JBIDE-20970 ;-) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] > ------------------------------------------------------- > > Key: JBIDE-20960 > URL: https://issues.jboss.org/browse/JBIDE-20960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Forge]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:47:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 16:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20542) Allow a user to add environment variables in deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill reassigned JBIDE-20542: ------------------------------------- Assignee: Jeff Cantrill > Allow a user to add environment variables in deploy image wizard > ---------------------------------------------------------------- > > Key: JBIDE-20542 > URL: https://issues.jboss.org/browse/JBIDE-20542 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:47:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 16:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20542) Allow a user to add environment variables in deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20542: ---------------------------------- Description: Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. * Also only remove those which were added * Only reset those which are defaults * Edit via double click was:Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. > Allow a user to add environment variables in deploy image wizard > ---------------------------------------------------------------- > > Key: JBIDE-20542 > URL: https://issues.jboss.org/browse/JBIDE-20542 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 16:57:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 15 Oct 2015 16:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118879#comment-13118879 ] George Gastaldi commented on JBIDE-20960: ----------------------------------------- Thanks. Will do. My point is that it would be nice to have issues like these created with a larger timegap from the release. Running the command is surely fast but it takes some time to switch contexts and understand what should be done. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] > ------------------------------------------------------- > > Key: JBIDE-20960 > URL: https://issues.jboss.org/browse/JBIDE-20960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Forge]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 17:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 17:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20971) Knowledge Base validation preference is ignored In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20971: -------------------------------------- Summary: Knowledge Base validation preference is ignored Key: JBIDE-20971 URL: https://issues.jboss.org/browse/JBIDE-20971 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 1. Create two java project, Project1 and Project2 2. Project1 depends on Project2 3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base) 4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2. 5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator 6. Uncheck Enable Validation 7. Clean/rebuild Project1 8. FAILURE: The warning is still there If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears. It looks like when we disable the KB validator at all then the old warning is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 17:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 17:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20971) Knowledge Base validation preference is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20971: ----------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > Knowledge Base validation preference is ignored > ----------------------------------------------- > > Key: JBIDE-20971 > URL: https://issues.jboss.org/browse/JBIDE-20971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > 1. Create two java project, Project1 and Project2 > 2. Project1 depends on Project2 > 3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base) > 4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2. > 5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator > 6. Uncheck Enable Validation > 7. Clean/rebuild Project1 > 8. FAILURE: The warning is still there > If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears. > It looks like when we disable the KB validator at all then the old warning is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 17:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 17:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20913) Knowledge Base validation preference is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20913: ----------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Knowledge Base validation preference is ignored > ----------------------------------------------- > > Key: JBIDE-20913 > URL: https://issues.jboss.org/browse/JBIDE-20913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Beta1 > > > 1. Create two java project, Project1 and Project2 > 2. Project1 depends on Project2 > 3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base) > 4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2. > 5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator > 6. Uncheck Enable Validation > 7. Clean/rebuild Project1 > 8. FAILURE: The warning is still there > If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears. > It looks like when we disable the KB validator at all then the old warning is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 17:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 17:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20971) Knowledge Base validation preference is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20971. ------------------------------------ Resolution: Done > Knowledge Base validation preference is ignored > ----------------------------------------------- > > Key: JBIDE-20971 > URL: https://issues.jboss.org/browse/JBIDE-20971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > 1. Create two java project, Project1 and Project2 > 2. Project1 depends on Project2 > 3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base) > 4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2. > 5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator > 6. Uncheck Enable Validation > 7. Clean/rebuild Project1 > 8. FAILURE: The warning is still there > If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears. > It looks like when we disable the KB validator at all then the old warning is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 17:30:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 15 Oct 2015 17:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20542) Allow a user to add environment variables in deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20542: ---------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > Allow a user to add environment variables in deploy image wizard > ---------------------------------------------------------------- > > Key: JBIDE-20542 > URL: https://issues.jboss.org/browse/JBIDE-20542 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.x > > > Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 17:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 15 Oct 2015 17:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118905#comment-13118905 ] Alexey Kazakov commented on JBIDE-20609: ---------------------------------------- Thanks for the video! Much easier to discuss your proposal now ;-) I like this overall. Not sure about the Manage Early Access link. What if we move it to the same place we currently use for "Enable EA"? But anyway IMO it's already good enough to have it in 4.3.1 and 4.4.0. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 20:01:01 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Thu, 15 Oct 2015 20:01:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118907#comment-13118907 ] Misha Ali commented on JBIDE-20609: ----------------------------------- Saw the video and it's really helpful towards understanding the scope of this JIRA. +1 from docs! > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 21:26:01 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 15 Oct 2015 21:26:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi closed JBIDE-20960. ----------------------------------- Resolution: Done Thanks [~nickboldt] > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] > ------------------------------------------------------- > > Key: JBIDE-20960 > URL: https://issues.jboss.org/browse/JBIDE-20960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Forge]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 21:27:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 15 Oct 2015 21:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20970) Upgrade Forge Runtime to 2.20.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118916#comment-13118916 ] George Gastaldi commented on JBIDE-20970: ----------------------------------------- Done, thanks [~akazakov] > Upgrade Forge Runtime to 2.20.0.Final > ------------------------------------- > > Key: JBIDE-20970 > URL: https://issues.jboss.org/browse/JBIDE-20970 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 21:27:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 15 Oct 2015 21:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20970) Upgrade Forge Runtime to 2.20.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi resolved JBIDE-20970. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 2.20.0.Final > ------------------------------------- > > Key: JBIDE-20970 > URL: https://issues.jboss.org/browse/JBIDE-20970 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 02:30:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 02:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20972) As a user I want to see relevant but simple info about my server adapter in the servers view In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-20972: ---------------------------------------- Summary: As a user I want to see relevant but simple info about my server adapter in the servers view Key: JBIDE-20972 URL: https://issues.jboss.org/browse/JBIDE-20972 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Alpha1 Reporter: Jeff Cantrill Fix For: 4.3.x Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 02:33:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 02:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20972) As a user I want to see relevant but simple info about my server adapter in the servers view In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20972: ------------------------------------- Attachment: (was: Pipeline view mockup.png) > As a user I want to see relevant but simple info about my server adapter in the servers view > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20972 > URL: https://issues.jboss.org/browse/JBIDE-20972 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 02:33:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 02:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20972) As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20972: ------------------------------------- Summary: As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view (was: As a user I want to see relevant but simple info about my server adapter in the servers view) > As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20972 > URL: https://issues.jboss.org/browse/JBIDE-20972 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 02:49:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Fri, 16 Oct 2015 02:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20973) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-20973: ------------------------------------- Summary: OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project Key: JBIDE-20973 URL: https://issues.jboss.org/browse/JBIDE-20973 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Mari?n Labuda Assignee: Jeff Cantrill Priority: Critical Fix For: 4.3.x Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: !deploy_image.png! If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 02:49:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Fri, 16 Oct 2015 02:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20973) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20973: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20973 > URL: https://issues.jboss.org/browse/JBIDE-20973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker > Fix For: 4.4.0.Alpha1 > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 02:49:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Fri, 16 Oct 2015 02:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20973) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda resolved JBIDE-20973. ----------------------------------- Resolution: Done > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20973 > URL: https://issues.jboss.org/browse/JBIDE-20973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker > Fix For: 4.4.0.Alpha1 > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 03:21:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 03:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118937#comment-13118937 ] Andre Dietisheim commented on JBIDE-20597: ------------------------------------------ We should add the connection page as 1st page to this wizard. The connection page allows all required operations: select an existing, edit it or create a new connection. We already do this in OpenShift v2 where one launches the application wizard from File->New->OpenShift or Central. We present the connection wizard page in the first place while we dont if the user launches the app wizard from context menu where we know about the connection that shall be used. > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 03:25:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 03:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118937#comment-13118937 ] Andre Dietisheim edited comment on JBIDE-20597 at 10/16/15 3:24 AM: -------------------------------------------------------------------- We should add the connection page as 1st page to this wizard. The connection page allows all required operations: select an existing, edit it or create a new connection. We already do this in OpenShift v2 where one launches the application wizard from File->New->OpenShift or Central. We present the connection wizard page in the first place while we dont if the user launches the app wizard from context menu where we know about the connection that shall be used. was (Author: adietish): We should add the connection page as 1st page to this wizard. The connection page allows all required operations: select an existing, edit it or create a new connection. We already do this in OpenShift v2 where one launches the application wizard from File->New->OpenShift or Central. We present the connection wizard page in the first place while we dont if the user launches the app wizard from context menu where we know about the connection that shall be used. > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 03:43:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Fri, 16 Oct 2015 03:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20698) tools.jboss.org/features: Add WildFly 9, 10 and EAP 7 to the list of supported servers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed JBIDE-20698. --------------------------------- My PR (note about EAP 7 and WF 10 being experimental) is merged now. Closing. > tools.jboss.org/features: Add WildFly 9,10 and EAP 7 to the list of supported servers > ------------------------------------------------------------------------------------- > > Key: JBIDE-20698 > URL: https://issues.jboss.org/browse/JBIDE-20698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Fix For: 4.3.0.Final > > > We should update http://tools.jboss.org/features/server.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 04:20:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 16 Oct 2015 04:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118949#comment-13118949 ] Max Rydahl Andersen commented on JBDS-3538: ------------------------------------------- okey, so the exact url we have problems with is: {code} https://download.jboss.org/tools/static/mars/stable/updates/core/4.3.0.Final/plugins/ternjs_1.0.0.201508302102.jar {code} I can download this file but it will not unzip. {code} ~/temp ??? unzip -l ternjs_1.0.0.201508302102.jar ? Archive: ternjs_1.0.0.201508302102.jar End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of ternjs_1.0.0.201508302102.jar or ternjs_1.0.0.201508302102.jar.zip, and cannot find ternjs_1.0.0.201508302102.jar.ZIP, period. {code} {code} size: 2625536 MD5 (ternjs_1.0.0.201508302102.jar) = 9b35dedb1a589cf27353ccc76db4bc3f IP: 178.197.228.237 {code} When rhopp downloads it works for him and he has different values: {code} size: 12893822 MD5 (ternjs_1.0.0.201508302102.jar) = c1a84f0cfee1957949e838ed26c3dfd4 IP: 94.113.217.17 {code} Both of these downloads was around 10:10 CET. > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 04:23:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Fri, 16 Oct 2015 04:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-520. ----------------------------------- Verified with JBDS 9.0.0.GA + JBDS-IS 9.0.0.Alpha2 > developer urls in our stable stream > ----------------------------------- > > Key: JBTIS-520 > URL: https://issues.jboss.org/browse/JBTIS-520 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.Alpha2, 9.0.0.GA > > Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, ea.png, non-ea.png, non-ea2.png > > > JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210 > earlyaccess is correct, but not the main IS site. > according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9. > Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release. > Please make sure we do not cross these streams. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 04:23:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Fri, 16 Oct 2015 04:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-521) Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-521. ----------------------------------- Closed as duplicated > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral > ------------------------------------------------------------------------------- > > Key: JBTIS-521 > URL: https://issues.jboss.org/browse/JBTIS-521 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Environment: JBDS 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.0.Alpha2 > > > Wrong update sites are added after installing JBDS-IS 9.0.0.Alpha2 from cantral. In Preferences > Available Software Sites I see the following sites > - https://devstudio.redhat.com/9.0/stable/updates/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/discovery/earlyaccess/ > The correct sites should be > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > - https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 04:26:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 16 Oct 2015 04:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118956#comment-13118956 ] Max Rydahl Andersen commented on JBDS-3538: ------------------------------------------- At the time of the download above I was in Grenoble, France on the mobile network and rhopp above is in Brno in Red Hat office. > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 04:48:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Fri, 16 Oct 2015 04:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-504. ----------------------------------- Verified with JBDS 9.0.0.GA + JBDS-IS 9.0.0.Alpha2 and with Eclipse Mars-1 JEE + JBoss Tools 4.3.0.Final (from Marketplace) + JBT-IS 4.3.0.Alpha2. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha2, 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 04:51:01 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Fri, 16 Oct 2015 04:51:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20729) Investigate ProcessInformationStore for its uses and whether it can be replaced In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118963#comment-13118963 ] Martin Malina commented on JBIDE-20729: --------------------------------------- Note for myself: When verifying this JIRA, I should check that the scenario from JBIDE-20754 works now - error is no longer thrown in console when having space in java path on Windows. > Investigate ProcessInformationStore for its uses and whether it can be replaced > ------------------------------------------------------------------------------- > > Key: JBIDE-20729 > URL: https://issues.jboss.org/browse/JBIDE-20729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > https://issues.jboss.org/browse/JBIDE-20510 was opened for a small bug regarding spaces on windows, but it revealed to me that the java8 I have installed there lacks a jps command. This means we need to revisit whether or not the ProcessInformationSotre is the proper solution for what it is doing, or if we can replace it with the debug code in jbt-base. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 04:53:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Fri, 16 Oct 2015 04:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20754) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed JBIDE-20754. --------------------------------- This is not really a duplicate. It's rather Won't fix or Out of date, since you remove ProcessInformationStore in JBIDE-20729 . But it's not too important - what matters is that this thing (error is gone) will be verified in that JIRA. > org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2 > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20754 > URL: https://issues.jboss.org/browse/JBIDE-20754 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Beta2 > Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.Beta1 > > > org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces. > In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows. > {noformat} > java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at java.lang.Runtime.exec(Runtime.java:450) > at java.lang.Runtime.exec(Runtime.java:347) > at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97) > at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) > at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.(ProcessImpl.java:386) > at java.lang.ProcessImpl.start(ProcessImpl.java:137) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 7 more > {noformat} > I'm note sure what the impact is - I don't necessarily notice anything not working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 05:10:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Fri, 16 Oct 2015 05:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-501) stable URLs used for Integration Stack installs/updates via Central should not contain a version number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-501. ----------------------------------- Verified > stable URLs used for Integration Stack installs/updates via Central should not contain a version number > ------------------------------------------------------------------------------------------------------- > > Key: JBTIS-501 > URL: https://issues.jboss.org/browse/JBTIS-501 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.2.3.Final , 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Stable URLs used for Integration Stack installs/updates via Central should not contain a version number, so that users only see ONE URL, which is updated to contain new, fresh content. > This allows new users to see the latest updates, existing users to see newer updates (Help > Check for updates), and existing users to seek new updates in Central, too. > So... > {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L82} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/{code} > Needs to change to > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > And http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ needs to be a composite of http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 05:36:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 05:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20596: ------------------------------------- Workaround Description: There are several ways to workaround this issues: a) Check and uncheck checkbox for a default server usage b) Switch to Basic authentication method and then switch to OAuth again - because token is cached, the Next button gets enabled. c) Instead of pasting token, type it. Or remove last character and type it again, then the Next button gets enabled. was: There are several ways to workaround this issues: a) Check and uncheck checkbox for a default server usage b) Switch to Basic authentication method and then switch to OAuth again - because token is cached, the Next button gets enabled. c) Instead of pasting token, paste it. Or remove last character and type it again, then the Next button gets enabled. > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 05:36:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Fri, 16 Oct 2015 05:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20922) [website] need a default landing page in whatsnew folder In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon updated JBIDE-20922: ---------------------------------- Fix Version/s: 4.4.x > [website] need a default landing page in whatsnew folder > -------------------------------------------------------- > > Key: JBIDE-20922 > URL: https://issues.jboss.org/browse/JBIDE-20922 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Xavier Coulon > Fix For: 4.4.x > > > This page is blank / forbidden: > http://tools.jboss.org/documentation/whatsnew/jbosstools/ > Yet this page is fine. > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html > Could we have a default index.html that redirects to the latest whatsnew version, so it's easier to link to the latest w/o knowing the version? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 05:36:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 05:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20596: ------------------------------------- Workaround Description: There are several ways to workaround this issues: a) Check and uncheck checkbox for a default server usage b) Switch to Basic authentication method and then switch to OAuth again - because token is cached, the Next button gets enabled. c) Instead of pasting token, type it. Or remove last character and type it again or check&uncheck "Save Token". -> then the Next button gets enabled. was: There are several ways to workaround this issues: a) Check and uncheck checkbox for a default server usage b) Switch to Basic authentication method and then switch to OAuth again - because token is cached, the Next button gets enabled. c) Instead of pasting token, type it. Or remove last character and type it again, then the Next button gets enabled. > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 05:47:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 05:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118979#comment-13118979 ] Andre Dietisheim commented on JBIDE-20596: ------------------------------------------ I can reproduce this too unfortunately. It's annoying but not critical though since the workaround is practicable though (ex. Toggle "Save Token") > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 05:59:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 16 Oct 2015 05:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118983#comment-13118983 ] Max Rydahl Andersen commented on JBIDE-20609: --------------------------------------------- Question: The video don't show what happens if I disable earlyaccess - will I still be proposed earlyaccess content when installing ? Also how does it handle when there is a "non-installable connector" vs "earlyaccess connector" ? Suggestion: don't force users to see the detailed earlyaccess info just to turn it off. Have a checkbox with "Show earlyaccess" and earlyaccess underlined. Have it on by default (opposite to what we had until now), clicking earlyaccess get you to the detailed dialog for more info and unchecking the checkbox = disable earlyaccess and after that EA won't be suggested to install. WDYT ? > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 06:03:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 06:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118986#comment-13118986 ] Andre Dietisheim commented on JBIDE-20596: ------------------------------------------ Technically speaking this is rather weird, it looks as if the container-buttons are not updated correctly. I see the global validity being VALID while "Next" isn't updated to enabled. > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:13:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Fri, 16 Oct 2015 07:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20950) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [VPE] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov reassigned JBIDE-20950: ---------------------------------------------- Assignee: Konstantin Marmalyukov > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [VPE] > ----------------------------------------------------- > > Key: JBIDE-20950 > URL: https://issues.jboss.org/browse/JBIDE-20950 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [VPE]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22visual-page-editor-core%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:21:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Fri, 16 Oct 2015 07:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20962) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [BrowserSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov reassigned JBIDE-20962: ---------------------------------------------- Assignee: Konstantin Marmalyukov > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [BrowserSim] > ------------------------------------------------------------ > > Key: JBIDE-20962 > URL: https://issues.jboss.org/browse/JBIDE-20962 > 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: > 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22browsersim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:22:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Fri, 16 Oct 2015 07:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20962) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [BrowserSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov closed JBIDE-20962. ------------------------------------------ Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [BrowserSim] > ------------------------------------------------------------ > > Key: JBIDE-20962 > URL: https://issues.jboss.org/browse/JBIDE-20962 > 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: > 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22browsersim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:41:00 2015 From: issues at jboss.org (Konstantin Marmalyukov (JIRA)) Date: Fri, 16 Oct 2015 07:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20950) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [VPE] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Marmalyukov closed JBIDE-20950. ------------------------------------------ Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [VPE] > ----------------------------------------------------- > > Key: JBIDE-20950 > URL: https://issues.jboss.org/browse/JBIDE-20950 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [VPE]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22visual-page-editor-core%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:48:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 07:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20956) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [OpenShift] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim reassigned JBIDE-20956: ---------------------------------------- Assignee: Andre Dietisheim > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [OpenShift] > ----------------------------------------------------------- > > Key: JBIDE-20956 > URL: https://issues.jboss.org/browse/JBIDE-20956 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [OpenShift]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22openshift%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:58:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 07:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18526) CordovaSim: Debugger doesn't work properly with the last JDK 8u20 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-18526: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > CordovaSim: Debugger doesn't work properly with the last JDK 8u20 > ----------------------------------------------------------------- > > Key: JBIDE-18526 > URL: https://issues.jboss.org/browse/JBIDE-18526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim, upstream > Affects Versions: 4.2.0.CR2 > Environment: Not reproducible with Oracle JDK 7u67 > Affects Oracle JDK 8u20 and above (Not reproducible with JDK 8u5 and 8u11) > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Labels: upstream > Fix For: 4.4.x > > Attachments: debugger error.png > > > CordovaSim freezes with the following stack trace: > {code} > java.lang.IllegalStateException: Nested event loops are allowed only while handling system events > at com.sun.javafx.tk.quantum.QuantumToolkit.enterNestedEventLoop(QuantumToolkit.java:506) > at com.sun.javafx.webkit.EventLoopImpl.cycle(EventLoopImpl.java:59) > at com.sun.webkit.EventLoop.fwkCycle(EventLoop.java:45) > at com.sun.webkit.Timer.twkFireTimerEvent(Native Method) > at com.sun.webkit.Timer.fireTimerEvent(Timer.java:83) > at com.sun.webkit.Timer.notifyTick(Timer.java:64) > at javafx.scene.web.WebEngine$PulseTimer.lambda$static$44(WebEngine.java:1167) > at javafx.scene.web.WebEngine$PulseTimer$$Lambda$67/10449826.pulse(Unknown Source) > at com.sun.javafx.tk.Toolkit.lambda$runPulse$28(Toolkit.java:314) > at com.sun.javafx.tk.Toolkit$$Lambda$134/26908315.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at com.sun.javafx.tk.Toolkit.runPulse(Toolkit.java:313) > at com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:340) > at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:451) > at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:431) > at com.sun.javafx.tk.quantum.QuantumToolkit.lambda$runToolkit$363(QuantumToolkit.java:298) > at com.sun.javafx.tk.quantum.QuantumToolkit$$Lambda$40/33541029.run(Unknown Source) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:59:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 07:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-13887) BrowserSim: Native code crash while opening some web pages on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-13887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-13887: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > BrowserSim: Native code crash while opening some web pages on Windows > --------------------------------------------------------------------- > > Key: JBIDE-13887 > URL: https://issues.jboss.org/browse/JBIDE-13887 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.0.0.Final > Environment: Windows 7 64-bit > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.4.x > > Attachments: JBIDE-13887.zip > > > Open http://www.html5rocks.com/en/tutorials/webdatabase/todo/ in BrowserSim. > BrowserSim closes with the following native error: > {code:title=Console Output} > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5dec02d7, pid=4356, tid=6572 > # > # JRE version: 6.0_35-b10 > # Java VM: Java HotSpot(TM) Client VM (20.10-b01 mixed mode, sharing windows-x86 ) > # Problematic frame: > # C [WebKit.dll+0x2702d7] > # > # An error report file with more information is saved as: > # D:\Doc\JBoss\git\jbosstools-vpe\plugins\org.jboss.tools.vpe.browsersim\hs_err_pid4356.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > {code} > {code:title=hs_err_pid4356.log} > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5dec02d7, pid=4356, tid=6572 > # > # JRE version: 6.0_35-b10 > # Java VM: Java HotSpot(TM) Client VM (20.10-b01 mixed mode, sharing windows-x86 ) > # Problematic frame: > # C [WebKit.dll+0x2702d7] > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > --------------- T H R E A D --------------- > Current thread (0x02249800): JavaThread "main" [_thread_in_native, id=6572, stack(0x02170000,0x021c0000)] > siginfo: ExceptionCode=0xc0000005, reading address 0x00000018 > Registers: > EAX=0x00000000, EBX=0x00000000, ECX=0x7ee2e000, EDX=0x00000000 > ESP=0x021bf8b0, EBP=0x021bf8f8, ESI=0x7ee2e000, EDI=0x00000000 > EIP=0x5dec02d7, EFLAGS=0x00210246 > Top of Stack: (sp=0x021bf8b0) > 0x021bf8b0: 7ee2e000 00000101 7ee2e000 00c98d26 > 0x021bf8c0: 00000164 00000080 0000013b 00000000 > 0x021bf8d0: 00000000 00000164 0000013b 00000000 > 0x021bf8e0: 00000005 00000164 0000013b 00000000 > 0x021bf8f0: 00000005 00000164 7ee8ed80 5debfdf6 > 0x021bf900: 00000000 5e394bf8 00000164 00e2e000 > 0x021bf910: 5de4db83 00000101 7ee8eda4 7ee8ed80 > 0x021bf920: 021bf994 021bf9d0 0000013b 00000137 > Instructions: (pc=0x5dec02d7) > 0x5dec02b7: 89 44 24 18 8d 44 24 18 89 4c 24 24 50 8b ce 89 > 0x5dec02c7: 7c 24 20 89 5c 24 24 ff d2 8b ce e8 89 fa ff ff > 0x5dec02d7: 8a 50 18 8a da c0 eb 02 80 e3 01 80 ca 04 84 db > 0x5dec02e7: 88 50 18 75 0b 6a 00 6a 01 8b c8 e8 59 9b ea ff > Register to memory mapping: > EAX=0x00000000 is an unknown value > EBX=0x00000000 is an unknown value > ECX=0x7ee2e000 is an unknown value > EDX=0x00000000 is an unknown value > ESP=0x021bf8b0 is pointing into the stack for thread: 0x02249800 > EBP=0x021bf8f8 is pointing into the stack for thread: 0x02249800 > ESI=0x7ee2e000 is an unknown value > EDI=0x00000000 is an unknown value > Stack: [0x02170000,0x021c0000], sp=0x021bf8b0, free space=318k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) > C [WebKit.dll+0x2702d7] WKOpenPanelResultListenerGetTypeID+0xbd537 > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.swt.internal.win32.OS.DispatchMessageW(Lorg/eclipse/swt/internal/win32/MSG;)I+0 > j org.eclipse.swt.internal.win32.OS.DispatchMessage(Lorg/eclipse/swt/internal/win32/MSG;)I+7 > j org.eclipse.swt.widgets.Display.readAndDispatch()Z+64 > j org.jboss.tools.vpe.browsersim.ui.BrowserSim.main([Ljava/lang/String;)V+175 > v ~StubRoutines::call_stub > --------------- P R O C E S S --------------- > Java Threads: ( => current thread ) > 0x023f3c00 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=6492, stack(0x04900000,0x04950000)] > 0x023d9c00 JavaThread "C1 CompilerThread0" daemon [_thread_blocked, id=6916, stack(0x04870000,0x048c0000)] > 0x023d8c00 JavaThread "Attach Listener" daemon [_thread_blocked, id=6208, stack(0x047e0000,0x04830000)] > 0x023d5800 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1636, stack(0x04750000,0x047a0000)] > 0x023cb000 JavaThread "Finalizer" daemon [_thread_blocked, id=6296, stack(0x046c0000,0x04710000)] > 0x023c9400 JavaThread "Reference Handler" daemon [_thread_blocked, id=7864, stack(0x04630000,0x04680000)] > =>0x02249800 JavaThread "main" [_thread_in_native, id=6572, stack(0x02170000,0x021c0000)] > Other Threads: > 0x0238d800 VMThread [stack: 0x045a0000,0x045f0000] [id=6248] > 0x023fcc00 WatcherThread [stack: 0x04990000,0x049e0000] [id=7820] > VM state:not at safepoint (normal execution) > VM Mutex/Monitor currently owned by a thread: None > Heap > def new generation total 4928K, used 3594K [0x241a0000, 0x246f0000, 0x296f0000) > eden space 4416K, 76% used [0x241a0000, 0x244eb190, 0x245f0000) > from space 512K, 43% used [0x245f0000, 0x24627850, 0x24670000) > to space 512K, 0% used [0x24670000, 0x24670000, 0x246f0000) > tenured generation total 10944K, used 1000K [0x296f0000, 0x2a1a0000, 0x341a0000) > the space 10944K, 9% used [0x296f0000, 0x297ea298, 0x297ea400, 0x2a1a0000) > compacting perm gen total 12288K, used 4013K [0x341a0000, 0x34da0000, 0x381a0000) > the space 12288K, 32% used [0x341a0000, 0x3458b568, 0x3458b600, 0x34da0000) > ro space 10240K, 55% used [0x381a0000, 0x38720f00, 0x38721000, 0x38ba0000) > rw space 12288K, 55% used [0x38ba0000, 0x392442f0, 0x39244400, 0x397a0000) > Code Cache [0x02450000, 0x02540000, 0x04450000) > total_blobs=400 nmethods=240 adapters=96 free_code_cache=32575872 largest_free_block=0 > Dynamic libraries: > 0x00400000 - 0x00425000 d:\progs\Programming\jdk1.6.0\bin\javaw.exe > 0x76fc0000 - 0x77140000 C:\Windows\SysWOW64\ntdll.dll > 0x75090000 - 0x751a0000 C:\Windows\syswow64\kernel32.dll > 0x75350000 - 0x75397000 C:\Windows\syswow64\KERNELBASE.dll > 0x74ff0000 - 0x75090000 C:\Windows\syswow64\ADVAPI32.dll > 0x751a0000 - 0x7524c000 C:\Windows\syswow64\msvcrt.dll > 0x754f0000 - 0x75509000 C:\Windows\SysWOW64\sechost.dll > 0x74f00000 - 0x74ff0000 C:\Windows\syswow64\RPCRT4.dll > 0x74a10000 - 0x74a70000 C:\Windows\syswow64\SspiCli.dll > 0x74a00000 - 0x74a0c000 C:\Windows\syswow64\CRYPTBASE.dll > 0x76290000 - 0x76390000 C:\Windows\syswow64\USER32.dll > 0x763d0000 - 0x76460000 C:\Windows\syswow64\GDI32.dll > 0x766f0000 - 0x766fa000 C:\Windows\syswow64\LPK.dll > 0x76a90000 - 0x76b2d000 C:\Windows\syswow64\USP10.dll > 0x76b60000 - 0x76bc0000 C:\Windows\system32\IMM32.DLL > 0x75280000 - 0x7534c000 C:\Windows\syswow64\MSCTF.dll > 0x7c340000 - 0x7c396000 d:\progs\Programming\jdk1.6.0\jre\bin\msvcr71.dll > 0x6d8c0000 - 0x6db6f000 d:\progs\Programming\jdk1.6.0\jre\bin\client\jvm.dll > 0x720e0000 - 0x72112000 C:\Windows\system32\WINMM.dll > 0x71e20000 - 0x71e6c000 C:\Windows\system32\apphelp.dll > 0x6d870000 - 0x6d87c000 d:\progs\Programming\jdk1.6.0\jre\bin\verify.dll > 0x6d3d0000 - 0x6d3ef000 d:\progs\Programming\jdk1.6.0\jre\bin\java.dll > 0x6d8b0000 - 0x6d8bf000 d:\progs\Programming\jdk1.6.0\jre\bin\zip.dll > 0x10000000 - 0x10070000 C:\Users\yradtsevich\.swt\lib\win32\x86\swt-win32-4234.dll > 0x74ac0000 - 0x74c1c000 C:\Windows\syswow64\ole32.dll > 0x76620000 - 0x766af000 C:\Windows\syswow64\OLEAUT32.dll > 0x74e20000 - 0x74e9b000 C:\Windows\syswow64\comdlg32.dll > 0x74ea0000 - 0x74ef7000 C:\Windows\syswow64\SHLWAPI.dll > 0x70db0000 - 0x70f4e000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll > 0x75510000 - 0x7615a000 C:\Windows\syswow64\SHELL32.dll > 0x72080000 - 0x720d1000 C:\Windows\system32\WINSPOOL.DRV > 0x76460000 - 0x76619000 C:\Windows\syswow64\WININET.dll > 0x76f90000 - 0x76f94000 C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll > 0x763c0000 - 0x763c5000 C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll > 0x753f0000 - 0x753f4000 C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll > 0x763b0000 - 0x763b4000 C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll > 0x74610000 - 0x74619000 C:\Windows\system32\version.DLL > 0x76700000 - 0x76703000 C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll > 0x766b0000 - 0x766b3000 C:\Windows\syswow64\normaliz.DLL > 0x74c20000 - 0x74e1e000 C:\Windows\syswow64\iertutil.dll > 0x768b0000 - 0x769ce000 C:\Windows\syswow64\CRYPT32.dll > 0x766e0000 - 0x766ec000 C:\Windows\syswow64\MSASN1.dll > 0x711e0000 - 0x71260000 C:\Windows\system32\uxtheme.dll > 0x10100000 - 0x1010e000 C:\Program Files\Logitech\SetPoint\x86\lgscroll.dll > 0x73420000 - 0x734bb000 C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll > 0x71d30000 - 0x71d51000 C:\Windows\system32\ntmarta.dll > 0x753a0000 - 0x753e5000 C:\Windows\syswow64\WLDAP32.dll > 0x71730000 - 0x71743000 C:\Windows\system32\dwmapi.dll > 0x71eb0000 - 0x71fa5000 C:\Windows\system32\propsys.dll > 0x76a00000 - 0x76a83000 C:\Windows\syswow64\CLBCatQ.DLL > 0x6a030000 - 0x6a05e000 C:\Windows\system32\mlang.dll > 0x72000000 - 0x7203c000 C:\Windows\system32\oleacc.dll > 0x05650000 - 0x05663000 C:\Users\yradtsevich\.swt\lib\win32\x86\swt-xulrunner-win32-4234.dll > 0x05670000 - 0x05684000 C:\Users\yradtsevich\.swt\lib\win32\x86\swt-webkit-win32-4234.dll > 0x5dc50000 - 0x5e4a5000 C:\Program Files (x86)\Safari\Apple Application Support\WebKit.dll > 0x736f0000 - 0x73950000 C:\Program Files (x86)\Safari\Apple Application Support\CFNetwork.dll > 0x74a70000 - 0x74aa5000 C:\Windows\syswow64\WS2_32.dll > 0x766c0000 - 0x766c6000 C:\Windows\syswow64\NSI.dll > 0x74620000 - 0x7463c000 C:\Windows\system32\iphlpapi.dll > 0x748a0000 - 0x748a7000 C:\Windows\system32\WINNSI.DLL > 0x735e0000 - 0x736e9000 C:\Program Files (x86)\Safari\Apple Application Support\CoreFoundation.dll > 0x735d0000 - 0x735e0000 C:\Program Files (x86)\Safari\Apple Application Support\pthreadVC2.dll > 0x69360000 - 0x69367000 C:\Windows\system32\WSOCK32.dll > 0x735b0000 - 0x735cd000 C:\Program Files (x86)\Safari\Apple Application Support\objc.dll > 0x73520000 - 0x735a7000 C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll > 0x74250000 - 0x7425e000 C:\Program Files (x86)\Safari\Apple Application Support\libdispatch.dll > 0x620b0000 - 0x621ea000 C:\Program Files (x86)\Safari\Apple Application Support\libicuin.dll > 0x60db0000 - 0x60e93000 C:\Program Files (x86)\Safari\Apple Application Support\libicuuc.dll > 0x4ad00000 - 0x4bc8b000 C:\Program Files (x86)\Safari\Apple Application Support\icudt46.dll > 0x73500000 - 0x73511000 C:\Program Files (x86)\Safari\Apple Application Support\ASL.dll > 0x61d20000 - 0x61d8f000 C:\Program Files (x86)\Safari\Apple Application Support\SQLite3.dll > 0x734e0000 - 0x734f4000 C:\Program Files (x86)\Safari\Apple Application Support\zlib1.dll > 0x5ebd0000 - 0x5ed03000 C:\Program Files (x86)\Safari\Apple Application Support\libxml2.dll > 0x5e810000 - 0x5ebc5000 C:\Program Files (x86)\Safari\Apple Application Support\CoreGraphics.dll > 0x5e690000 - 0x5e80b000 C:\Program Files (x86)\Safari\Apple Application Support\JavaScriptCore.dll > 0x60d80000 - 0x60da9000 C:\Program Files (x86)\Safari\Apple Application Support\WebKitQuartzCoreAdditions.dll > 0x5e540000 - 0x5e684000 C:\Program Files (x86)\Safari\Apple Application Support\QuartzCore.dll > 0x5db10000 - 0x5dc4f000 C:\Program Files (x86)\Safari\Apple Application Support\CoreVideo.dll > 0x71760000 - 0x71923000 C:\Windows\system32\d3d9.dll > 0x71750000 - 0x71756000 C:\Windows\system32\d3d8thk.dll > 0x6df70000 - 0x6e0a0000 C:\Windows\system32\WindowsCodecs.dll > 0x6fa50000 - 0x6fa62000 C:\Program Files (x86)\Common Files\TortoiseOverlays\TortoiseOverlays.dll > 0x6fa40000 - 0x6fa4d000 C:\Program Files\TortoiseSVN\bin\TortoiseStub32.dll > 0x6f9d0000 - 0x6fa3c000 C:\Program Files\TortoiseSVN\bin\TortoiseSVN32.dll > 0x6db80000 - 0x6de75000 C:\Program Files\TortoiseSVN\bin\libsvn_tsvn32.dll > 0x6f960000 - 0x6f984000 C:\Program Files\TortoiseSVN\bin\libapr_tsvn32.dll > 0x74310000 - 0x7434c000 C:\Windows\system32\MSWSOCK.dll > 0x747a0000 - 0x7485f000 C:\Windows\system32\MSVCR100.dll > 0x6f920000 - 0x6f956000 C:\Program Files\TortoiseSVN\bin\libaprutil_tsvn32.dll > 0x6f910000 - 0x6f91d000 C:\Program Files\TortoiseSVN\bin\intl3_tsvn32.dll > 0x6ef00000 - 0x6ef13000 C:\Program Files\TortoiseSVN\bin\libsasl32.dll > 0x71be0000 - 0x71be8000 C:\Windows\system32\Secur32.dll > 0x748c0000 - 0x74929000 C:\Windows\system32\MSVCP100.dll > 0x06860000 - 0x06882000 C:\Users\yradtsevich\AppData\Roaming\Dropbox\bin\DropboxExt.17.dll > 0x71c40000 - 0x71d2b000 C:\Windows\system32\dbghelp.dll > 0x6ede0000 - 0x6ee6e000 C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll > 0x6ed30000 - 0x6edd3000 C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll > 0x6eec0000 - 0x6eef1000 C:\Windows\system32\EhStorShell.dll > 0x76710000 - 0x768ad000 C:\Windows\syswow64\SETUPAPI.dll > 0x75250000 - 0x75277000 C:\Windows\syswow64\CFGMGR32.dll > 0x76390000 - 0x763a2000 C:\Windows\syswow64\DEVOBJ.dll > 0x06fc0000 - 0x073c6000 C:\PROGRA~2\MICROS~1\Office14\GROOVEEX.DLL > 0x6ee90000 - 0x6eebb000 C:\Windows\WinSxS\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.6161_none_51cd0a7abbe4e19b\ATL90.DLL > 0x6cf40000 - 0x6d35a000 C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE14\Cultures\office.odf > 0x6c6c0000 - 0x6cf38000 C:\PROGRA~2\MICROS~1\Office14\1049\GrooveIntlResource.dll > 0x74390000 - 0x7439b000 C:\Windows\system32\profapi.dll > 0x74290000 - 0x742a2000 C:\Windows\system32\dhcpcsvc.DLL > 0x74240000 - 0x7424d000 C:\Windows\system32\dhcpcsvc6.DLL > 0x676e0000 - 0x67759000 C:\Windows\system32\mscms.dll > 0x71d70000 - 0x71d87000 C:\Windows\system32\USERENV.dll > 0x734c0000 - 0x734d1000 C:\Windows\system32\Cryptdll.dll > 0x6fa70000 - 0x7050d000 C:\Windows\system32\igdumd32.dll > 0x74460000 - 0x74476000 C:\Windows\system32\CRYPTSP.dll > 0x74410000 - 0x7444b000 C:\Windows\system32\rsaenh.dll > 0x70b80000 - 0x70b84000 C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll > 0x74ab0000 - 0x74ab4000 C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll > 0x6e560000 - 0x6e564000 C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll > 0x74300000 - 0x74306000 C:\Windows\System32\wship6.dll > 0x6e500000 - 0x6e55a000 C:\Windows\System32\netprofm.dll > 0x70f50000 - 0x70f60000 C:\Windows\System32\nlaapi.dll > 0x71d90000 - 0x71d9e000 C:\Windows\system32\RpcRtRemote.dll > 0x6e4f0000 - 0x6e4f8000 C:\Windows\System32\npmproxy.dll > 0x74380000 - 0x74385000 C:\Windows\System32\wshtcpip.dll > 0x742b0000 - 0x742f4000 C:\Windows\system32\DNSAPI.dll > 0x70d30000 - 0x70d55000 C:\Program Files (x86)\Bonjour\mdnsNSP.dll > 0x70ce0000 - 0x70ce6000 C:\Windows\system32\rasadhlp.dll > 0x70cf0000 - 0x70d28000 C:\Windows\System32\fwpuclnt.dll > 0x6ef20000 - 0x6ef31000 C:\Program Files (x86)\Safari\Apple Application Support\QTMovieWin.dll > VM Arguments: > jvm_args: -Dfile.encoding=Cp1251 > java_command: org.jboss.tools.vpe.browsersim.ui.BrowserSim http://www.html5rocks.com/en/tutorials/webdatabase/todo/ > Launcher Type: SUN_STANDARD > Environment Variables: > JAVA_HOME=d:\progs\Programming\jdk1.6.0\ > PATH=D:/progs/Programming/jre1.7.0/bin/client;D:/progs/Programming/jre1.7.0/bin;D:/progs/Programming/jre1.7.0/lib/i386;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Broadcom\Broadcom 802.11\Driver;d:\progs\Programming\apache-maven-3.0.4\bin;C:\Program Files\TortoiseSVN\bin;D:\progs\Subversion\bin;d:\progs\Subversion\bin;d:\progs\Programming\Ruby-1.9.3\bin;d:\progs\MinGW\bin;d:\progs\MinGW\msys\1.0\bin;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;;d:\progs\Programming\WindowsAndroid\windowsandroid_root\system\bin;d:\progs\Programming\WindowsAndroid\windowsandroid_root\system\lib;C:\Progs\OpenVPN\bin;d:\Progs\OpenVPN\bin;d:\progs\Programming\eclipse-4.2.1; > USERNAME=yradtsevich > OS=Windows_NT > PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel > --------------- S Y S T E M --------------- > OS: Windows 7 , 64 bit Build 7601 Service Pack 1 > CPU:total 4 (2 cores per cpu, 2 threads per core) family 6 model 42 stepping 7, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, ht > Memory: 4k page, physical 8321400k(4289548k free), swap 16640948k(12054388k free) > vm_info: Java HotSpot(TM) Client VM (20.10-b01) for windows-x86 JRE (1.6.0_35-b10), built on Aug 28 2012 17:31:51 by "java_re" with MS VC++ 7.1 (VS2003) > time: Sat Mar 30 22:08:39 2013 > elapsed time: 1 seconds > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:59:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 07:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-14505) CordovaSim: Device API should know which device (BS skin) is selected In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-14505: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > CordovaSim: Device API should know which device (BS skin) is selected > --------------------------------------------------------------------- > > Key: JBIDE-14505 > URL: https://issues.jboss.org/browse/JBIDE-14505 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.x > > > Cordova's "Device API" ( http://docs.phonegap.com/en/3.0.0/cordova_device_device.md.html#Device ) should return different data for different devices (BS skins) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 07:59:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 07:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-14693) CordovaSim: implement audio / video capturing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-14693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-14693: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > CordovaSim: implement audio / video capturing > --------------------------------------------- > > Key: JBIDE-14693 > URL: https://issues.jboss.org/browse/JBIDE-14693 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Affects Versions: 4.1.0.Beta1 > Environment: JBT 4.1.0.Beta1a on Linux > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.4.x > > > See this link https://issues.jboss.org/browse/JBIDE-13552?focusedCommentId=12777758&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12777758 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:00:04 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:00:04 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-17054) Browsersim and type="date" results in a non-editable field for JavaFx web engine In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-17054: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Browsersim and type="date" results in a non-editable field for JavaFx web engine > -------------------------------------------------------------------------------- > > Key: JBIDE-17054 > URL: https://issues.jboss.org/browse/JBIDE-17054 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim, upstream > Affects Versions: 4.2.0.Beta1 > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.x > > > Browsersim and type="date" results in a non-editable field > > http://screencast.com/t/u9zLEbGAGXWJ > contacts-mobile-basic is a quickstart in WFK 2.5, downloadable from the customer portal. > https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.5.x/contacts-mobile-basic > JBoss Tools Mobile Browser Simulator 3.5.100.Beta1-v20140331-2229-B15 org.jboss.tools.vpe.browsersim.feature.feature.group JBoss by Red Hat > Related javaFX issue - https://javafx-jira.kenai.com/browse/RT-34974 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:00:04 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:00:04 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-17944) BrowserSim: Use http: protocol instead of file: for accessing local files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-17944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-17944: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > BrowserSim: Use http: protocol instead of file: for accessing local files > ------------------------------------------------------------------------- > > Key: JBIDE-17944 > URL: https://issues.jboss.org/browse/JBIDE-17944 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim > Affects Versions: 4.2.2.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.x > > Attachments: ripple.png > > > Currently, BrowserSim works through file: protocol but this protocol doesn't work well with paths relative to the webroot (which start with "/"). > So if a local file contains any links to local resources (css, js, ...) via relative paths then these resources are not available in BrowserSim. > For example all official ionic example projects use such paths. It makes "open with BrowserSim" feature useless for those projects. > It would be great if BrowserSim uses http: as our HTML5 preview does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:00:04 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:00:04 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18329) Ionic, tabs, CordovaSim, LiveReload, lost back button In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-18329: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Ionic, tabs, CordovaSim, LiveReload, lost back button > ----------------------------------------------------- > > Key: JBIDE-18329 > URL: https://issues.jboss.org/browse/JBIDE-18329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.CR1 > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.x > > > Using Ionic tabs starter/template > LiveReload > CordovaSim > to edit friend-detail.html > works almost awesome...but for the disappearing Back button > http://www.screencast.com/t/APqNTq7K3c > upsteam issue - https://github.com/driftyco/ionic/issues/3222 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:00:04 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:00:04 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19032) CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-19032: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-19032 > URL: https://issues.jboss.org/browse/JBIDE-19032 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.x > > > see the following [comment|https://issues.jboss.org/browse/JBIDE-18900?focusedCommentId=13031830&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13031830] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:00:05 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:00:05 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19087) Debugging Ionic Project With CordovaSim and Livereload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-19087: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Debugging Ionic Project With CordovaSim and Livereload > ------------------------------------------------------ > > Key: JBIDE-19087 > URL: https://issues.jboss.org/browse/JBIDE-19087 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.2.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.x > > > The issue was created on top of the thread on developer.jboss.org - https://developer.jboss.org/thread/251880 > Basically, the issue is tightly coupled with the upstream - https://github.com/driftyco/ionic/issues/3222 (ionic history state lose). > *Upstream issue:* https://github.com/driftyco/ionic/issues/3222 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:01:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18556) battery status is not reflected in browsersim's status bar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-18556: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > battery status is not reflected in browsersim's status bar > ---------------------------------------------------------- > > Key: JBIDE-18556 > URL: https://issues.jboss.org/browse/JBIDE-18556 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.4.x > > Attachments: log.png > > > create basic cordova app. > run in cordova sim. > changing the battery level and is-plugged does not take effect in the simulator. > Should it not be able to detect these ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:02:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18583) pong index.html no longer works on cordovasim (Mac OS specific) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-18583: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > pong index.html no longer works on cordovasim (Mac OS specific) > --------------------------------------------------------------- > > Key: JBIDE-18583 > URL: https://issues.jboss.org/browse/JBIDE-18583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.CR2 > Environment: Mac Os > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.4.x > > Attachments: index.html.zip > > > This works in previous versions. > replace the index.html into a hybrid app - it works when using ios simulator but not with cordovasim. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:06:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 16 Oct 2015 08:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20584) CordovaSim doesn't talk to remote FH cloud app In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20584: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > CordovaSim doesn't talk to remote FH cloud app > ---------------------------------------------- > > Key: JBIDE-20584 > URL: https://issues.jboss.org/browse/JBIDE-20584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.x > > Attachments: remote.png > > > I found several issue connected with CordovaSim FH & cordova.js >= 4.0.0: > -1) Running against *local* FH cloud app fails with disabled proxy (need to use local by default)- (UPD: reported as a separated issue - JBIDE-20590) > 2) Running against *remote* FH cloud app does not work with cordovasim at all (for remote proxy the error is the following): > {code} > XMLHttpRequest cannot load https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_?3A//aerogear-t-uy2f2glr7qrvs4k6rvfnj3ya-dev.ac.gen.ric.feedhenry.com/hello. Cannot use wildcard in Access-Control-Allow-Origin when credentials flag is true. > {code} > -Literally, this cordova hello world app does not work against FH app preview (It used to work before)- (UPD: not a bug the app must be deployed firstly - JBIDE-20606)!remote.png|thumbnail!*strong text* -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:27:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Fri, 16 Oct 2015 08:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20907) Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio resolved JBIDE-20907. ---------------------------------- Resolution: Done > Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20907 > URL: https://issues.jboss.org/browse/JBIDE-20907 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 08:28:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Fri, 16 Oct 2015 08:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20907) Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio closed JBIDE-20907. -------------------------------- > Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20907 > URL: https://issues.jboss.org/browse/JBIDE-20907 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 09:03:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Fri, 16 Oct 2015 09:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20974) Project combo not populated regression In-Reply-To: References: Message-ID: Jeff Cantrill created JBIDE-20974: ------------------------------------- Summary: Project combo not populated regression Key: JBIDE-20974 URL: https://issues.jboss.org/browse/JBIDE-20974 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.x Reporter: Jeff Cantrill Assignee: Jeff Cantrill Projects not correctly populated after fix to JBIDE-20714 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 09:22:00 2015 From: issues at jboss.org (Hardy Ferentschik (JIRA)) Date: Fri, 16 Oct 2015 09:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119071#comment-13119071 ] Hardy Ferentschik commented on JBIDE-19178: ------------------------------------------- Out of curiosity, is there no way to "inline" the properties view/editor into the tree? I would find it nice if I could view/edit config properties in the tree instead of getting switched to another tab. (mind you, I am saying that w/o any knowledge of potential Eclipse/UI limitations). > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 09:24:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 09:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119073#comment-13119073 ] Fred Bricon commented on JBIDE-20609: ------------------------------------- Video looks good. But also +1 for [~maxandersen]'s suggestion about getting the checkbox back on the page, along the link. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 09:26:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 09:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20714) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20714: -------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.x) > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20714 > URL: https://issues.jboss.org/browse/JBIDE-20714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker > Fix For: 4.3.1.Beta1 > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 09:27:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 09:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20974) Project combo not populated regression In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20974: -------------------------------- Fix Version/s: 4.3.1.Beta1 > Project combo not populated regression > -------------------------------------- > > Key: JBIDE-20974 > URL: https://issues.jboss.org/browse/JBIDE-20974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Projects not correctly populated after fix to JBIDE-20714 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 09:27:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 09:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20974) Project combo not populated regression In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20974: -------------------------------- Affects Version/s: 4.3.1.Beta1 (was: 4.3.x) > Project combo not populated regression > -------------------------------------- > > Key: JBIDE-20974 > URL: https://issues.jboss.org/browse/JBIDE-20974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Projects not correctly populated after fix to JBIDE-20714 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 10:06:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 10:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20846) merge v2 and v3 feature pages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20846: -------------------------------- Fix Version/s: 4.3.0.Final > merge v2 and v3 feature pages > ----------------------------- > > Key: JBIDE-20846 > URL: https://issues.jboss.org/browse/JBIDE-20846 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.0.Final > > > it is waste of valuable space to have both v2 and v3 on http://tools.jboss.org/features/ > Most of the content inside are exactly the same so seem simpler to just add a "For OSv3 we have Deploy Docker ..." or some other mechanism to highlight it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 10:09:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Fri, 16 Oct 2015 10:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20542) Allow a user to add environment variables in deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20542: ---------------------------------- Labels: docker merge_into_master (was: docker) > Allow a user to add environment variables in deploy image wizard > ---------------------------------------------------------------- > > Key: JBIDE-20542 > URL: https://issues.jboss.org/browse/JBIDE-20542 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker, merge_into_master > Fix For: 4.3.x > > > Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:09:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119133#comment-13119133 ] Andre Dietisheim commented on JBIDE-20596: ------------------------------------------ This error only occurrs where we launch the wizard from menu or central, when we use the delegating wizard page (which will invoke the v2 or v3 wizard based on the server type). > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:12:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119133#comment-13119133 ] Andre Dietisheim edited comment on JBIDE-20596 at 10/16/15 11:11 AM: --------------------------------------------------------------------- This error only occurrs where we launch the wizard from menu or central, when we use the delegating wizard page (which will invoke the v2 or v3 wizard based on the server type). The basic error is therefore in the DelegatingConnectionWizardPage was (Author: adietish): This error only occurrs where we launch the wizard from menu or central, when we use the delegating wizard page (which will invoke the v2 or v3 wizard based on the server type). > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:31:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119144#comment-13119144 ] Nick Boldt commented on JBIDE-20960: ------------------------------------ Beta1 code freeze is probably happening late November. Is 6 weeks not enough time to prepare? :P > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] > ------------------------------------------------------- > > Key: JBIDE-20960 > URL: https://issues.jboss.org/browse/JBIDE-20960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Forge]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:32:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119145#comment-13119145 ] Andre Dietisheim commented on JBIDE-19178: ------------------------------------------ [~hardy.ferentschik] sure thing, the Servers view is a tree that you can customize to your needs and have displaying whatever details you want. Nevertheless I'd still think that the simpler and focused it is the better. On top of that I believe that you wont edit these things on a regular base. > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:35:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3545) For JBDS 9.0.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBDS-3545. ---------------------------- Resolution: Done > For JBDS 9.0.1.Beta1: Prepare for future Beta1 > ---------------------------------------------- > > Key: JBDS-3545 > URL: https://issues.jboss.org/browse/JBDS-3545 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 9.0.1.Beta1 > > > For JBDS 9.0.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:43:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119154#comment-13119154 ] Andre Dietisheim commented on JBIDE-20596: ------------------------------------------ merged and pushed to upstream/jbosstools-4.3.1.x > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:43:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20975) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-20975: ---------------------------------------- Summary: Next button in the New OpenShift Application window is enabled only after clicking Use default server check box Key: JBIDE-20975 URL: https://issues.jboss.org/browse/JBIDE-20975 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Supriya Bharadwaj Assignee: Jeff Cantrill Fix For: 4.3.1.Beta1 In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:43:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20975) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20975: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20975 > URL: https://issues.jboss.org/browse/JBIDE-20975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:45:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20952) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20952. ------------------------------ Assignee: Nick Boldt Resolution: Done build, build-sites: done build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch: nothing to do. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20952 > URL: https://issues.jboss.org/browse/JBIDE-20952 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22build%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:48:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20975) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20975: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/791 (was: https://github.com/jbosstools/jbosstools-openshift/pull/778) > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20975 > URL: https://issues.jboss.org/browse/JBIDE-20975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:49:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20949) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central Discovery] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20949. ------------------------------ Assignee: Nick Boldt Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central Discovery] > ------------------------------------------------------------------- > > Key: JBIDE-20949 > URL: https://issues.jboss.org/browse/JBIDE-20949 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: discovery > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Central Discovery]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22discovery%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:53:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3531) versionwatch thinks JBDS 10 is older than JBDS 9 (1 < 9 instead of 10 > 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBDS-3531. ---------------------------- Resolution: Done Fixed. http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html now shows 10.0 as the newest version, not the oldest. > versionwatch thinks JBDS 10 is older than JBDS 9 (1 < 9 instead of 10 > 9) > -------------------------------------------------------------------------- > > Key: JBDS-3531 > URL: https://issues.jboss.org/browse/JBDS-3531 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-10.0.0.Alpha1.install.xml > > > In http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/2015-09-25_14-27-05_B2870_report_detailed_filtered.html we see versionwatch complaining that the version of com.jboss.devstudio.core.feature went DOWN from 10.0.0 to 9.0.0. > Obviously we need to fix the version diffing engine so it sees more than the first digit of the version, and therefore sees 10 > 9, rather than 1 < 9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:57:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20976: ---------------------------------- Summary: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 Key: JBIDE-20976 URL: https://issues.jboss.org/browse/JBIDE-20976 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt Priority: Critical Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). Details in these logs: http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html Affected IUs: {code} org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 org.eclipse.jst.web_core.feature 3.7.1.v201509021802 org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 org.eclipse.sapphire.java 9.0.1.201509151939 org.eclipse.jgit 4.0.2.201509141540-r org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 org.eclipse.sapphire.platform 9.0.1.201509151939 org.eclipse.rcp 4.5.1.v20150904-0015 org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 org.eclipse.sapphire 9.0.1.201509151939 org.eclipse.wst.server_core.feature 3.3.600.v201508271522 org.eclipse.wst.web_core.feature 3.7.1.v201508271605 org.eclipse.egit 4.0.2.201509141540-r org.eclipse.pde 3.11.1.v20150904-0345 org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 org.eclipse.sapphire.ui 9.0.1.201509151939 org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 org.eclipse.sapphire.java.jdt 9.0.1.201509151939 org.eclipse.wst.common_core.feature 3.7.1.v201508262220 org.eclipse.sapphire.osgi 9.0.1.201509151939 org.eclipse.jdt 3.11.1.v20150904-0015 org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 org.eclipse.egit.core 4.0.2.201509141540-r org.eclipse.wst.server.discovery 1.1.0.v201508271522 org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 org.eclipse.wst.server.core 1.7.0.v201508271522 org.eclipse.platform.doc.user 4.5.1.v20150819-1130 org.eclipse.platform 4.5.1.v20150904-0015 org.eclipse.core.runtime 3.11.1.v20150903-1804 org.eclipse.jetty.webapp 9.2.13.v20150730 org.eclipse.egit.ui 4.0.2.201509141540-r org.eclipse.rcp 4.5.1.v20150904-0015 org.eclipse.jdt 3.11.1.v20150904-0015 org.eclipse.sapphire.java.jdt 9.0.1.201509151939 org.eclipse.pde 3.11.1.v20150904-0015 org.eclipse.swt 3.104.1.v20150825-0743 org.eclipse.jetty.xml 9.2.13.v20150730 org.eclipse.sapphire.ui 9.0.1.201509151939 org.eclipse.egit.doc 4.0.2.201509141540-r org.eclipse.jgit.archive 4.0.2.201509141540-r org.eclipse.jgit 4.0.2.201509141540-r org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 org.eclipse.egit 4.0.2.201509141540-r org.eclipse.sapphire.workspace 9.0.1.201509151939 org.eclipse.wst.server.ui 1.5.201.v201509022125 org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 org.eclipse.sapphire.java 9.0.1.201509151939 org.eclipse.sapphire.modeling 9.0.1.201509151939 org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 org.eclipse.pde.doc.user 3.11.1.v20150903-1352 org.eclipse.wst.validation 1.2.700.v201508251749 org.eclipse.jst.common.frameworks 1.1.701.v201509021802 org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 org.eclipse.sapphire.platform 9.0.1.201509151939 org.eclipse.sapphire.osgi 9.0.1.201509151939 {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:57:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20976: ---------------------------------- Assignee: Mickael Istria > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:57:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Fix Version/s: 4.4.0.Alpha1 > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:58:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 11:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Component/s: upstream > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:59:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20975) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119159#comment-13119159 ] Andre Dietisheim commented on JBIDE-20975: ------------------------------------------ merged and pushed to upstream/master > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20975 > URL: https://issues.jboss.org/browse/JBIDE-20975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 11:59:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 11:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20975) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim resolved JBIDE-20975. -------------------------------------- Assignee: Andre Dietisheim (was: Jeff Cantrill) Resolution: Done > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20975 > URL: https://issues.jboss.org/browse/JBIDE-20975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 12:00:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 12:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119154#comment-13119154 ] Andre Dietisheim edited comment on JBIDE-20596 at 10/16/15 11:59 AM: --------------------------------------------------------------------- merged and pushed to upstream/jbosstools-4.3.x was (Author: adietish): merged and pushed to upstream/jbosstools-4.3.1.x > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 12:00:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 12:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim reassigned JBIDE-20596: ---------------------------------------- Assignee: Andre Dietisheim (was: Jeff Cantrill) > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta1 > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 12:08:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Fri, 16 Oct 2015 12:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20960) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119165#comment-13119165 ] George Gastaldi commented on JBIDE-20960: ----------------------------------------- Good to know that's your definition of ASAP ;) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge] > ------------------------------------------------------- > > Key: JBIDE-20960 > URL: https://issues.jboss.org/browse/JBIDE-20960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Forge]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22forge%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 12:09:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 12:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20956) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [OpenShift] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon closed JBIDE-20956. ------------------------------- Assignee: Fred Bricon (was: Andre Dietisheim) Resolution: Done Done in 4.3.x > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [OpenShift] > ----------------------------------------------------------- > > Key: JBIDE-20956 > URL: https://issues.jboss.org/browse/JBIDE-20956 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [OpenShift]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22openshift%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 12:09:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 12:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20966) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20966: ----------------------------------- Assignee: Fred Bricon > 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22maven%22%2C%22central%22%2C%22project-examples%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 12:29:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 12:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20966) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon closed JBIDE-20966. ------------------------------- Resolution: Done Done in 4.3.x > 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22maven%22%2C%22central%22%2C%22project-examples%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:26:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 13:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119181#comment-13119181 ] Fred Bricon commented on JBIDE-20923: ------------------------------------- For me, org.jboss.archetype.eap:jboss-javaee6-webapp-ear-archetype:6.4.0.GA is selected when choosing EAP 7, using latest JBDS 9. Could you screencast the issue? > Wrong archetype is picked for unreleased EAP (7) > ------------------------------------------------ > > Key: JBIDE-20923 > URL: https://issues.jboss.org/browse/JBIDE-20923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > > When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype). > Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:37:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20957: -------------------------------------- Assignee: Mickael Istria > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] > ------------------------------------------------------------ > > Key: JBIDE-20957 > URL: https://issues.jboss.org/browse/JBIDE-20957 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22playground%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:37:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20948: -------------------------------------- Assignee: Gorkem Ercan > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] > ---------------------------------------------------------- > > Key: JBIDE-20948 > URL: https://issues.jboss.org/browse/JBIDE-20948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Aerogear]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22aerogear-hybrid%22%2C%22cordovasim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20963) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20963: -------------------------------------- Assignee: Xavier Coulon > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] > ------------------------------------------------------------- > > Key: JBIDE-20963 > URL: https://issues.jboss.org/browse/JBIDE-20963 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Webservices]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22webservices%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20953) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20953: -------------------------------------- Assignee: Rob Stryker > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] > -------------------------------------------------------- > > Key: JBIDE-20953 > URL: https://issues.jboss.org/browse/JBIDE-20953 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Server]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22server%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20954) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Hibernate] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20954: -------------------------------------- Assignee: Koen Aers > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Hibernate] > ----------------------------------------------------------- > > Key: JBIDE-20954 > URL: https://issues.jboss.org/browse/JBIDE-20954 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Hibernate]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22hibernate%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20965) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Freemarker] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20965: -------------------------------------- Assignee: Denis Golovin > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Freemarker] > ------------------------------------------------------------ > > Key: JBIDE-20965 > URL: https://issues.jboss.org/browse/JBIDE-20965 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Freemarker]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22freemarker%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20967) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20967: -------------------------------------- Assignee: Xavier Coulon > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] > ------------------------------------------------------------ > > Key: JBIDE-20967 > URL: https://issues.jboss.org/browse/JBIDE-20967 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [LiveReload]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22livereload%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:46:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20977) XML identation size is not editable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20977: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20977 (was: JBDS-3166) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: upstream (was: upstream) Affects Version/s: 4.2.0.CR1 (was: 8.0.0.CR1) Fix Version/s: 4.4.x (was: 8.x) (was: 9.x) > XML identation size is not editable > ----------------------------------- > > Key: JBIDE-20977 > URL: https://issues.jboss.org/browse/JBIDE-20977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1b, Eclipse 4.4 > I have Fedora 19, Java 1.7_60, Gnome3, it is both case for JBDS 8.x and Eclipse 4.4 > Colleague of mine has RHEL7 with Gnome, tested on JBDS 8.x as well. > Reporter: Stefan Miklosovic > Assignee: Denis Golovin > Fix For: 4.4.x > > Attachments: xml-preferences.png > > > !xml-preferences.png! > Window -> Preferencies -> XML -> XML Files -> Editor > Ident using spaces is checked. > Identation size field is not editable, there is still "1" in it. Clicking at arrows (or + - buttons) does not work. I can not rise it to 4 spaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:48:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20977) XML identation size is not editable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20977: -------------------------------------- Assignee: Snjezana Peco (was: Denis Golovin) Looks like a swt/gtk issue in Eclipse reproducible in Fedora 19. [~snjeza] could you please take a look? [~dgolovin] have you created an ticket in bugzilla? > XML identation size is not editable > ----------------------------------- > > Key: JBIDE-20977 > URL: https://issues.jboss.org/browse/JBIDE-20977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1b, Eclipse 4.4 > I have Fedora 19, Java 1.7_60, Gnome3, it is both case for JBDS 8.x and Eclipse 4.4 > Colleague of mine has RHEL7 with Gnome, tested on JBDS 8.x as well. > Reporter: Stefan Miklosovic > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: xml-preferences.png > > > !xml-preferences.png! > Window -> Preferencies -> XML -> XML Files -> Editor > Ident using spaces is checked. > Identation size field is not editable, there is still "1" in it. Clicking at arrows (or + - buttons) does not work. I can not rise it to 4 spaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:52:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3057: --------------------------------- Fix Version/s: 10.x (was: 8.x) (was: 9.x) > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Denis Golovin > Labels: f2f2014 > Fix For: 10.x > > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:52:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 13:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20978) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-20978: ---------------------------------------- Summary: Connection wizard: switching to resets token but form is still valid Key: JBIDE-20978 URL: https://issues.jboss.org/browse/JBIDE-20978 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.3.1.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:52:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 13:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20978) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20978: ------------------------------------- Attachment: form-erroneously-valid.png > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:52:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 13:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20978) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20978: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: connection page shows up as 1st wizard page # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. was: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: connection page shows up as 1st wizard page # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3070) Mixed fonts in installer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3070: --------------------------------- Fix Version/s: LATER (was: 8.x) (was: 9.x) > Mixed fonts in installer > ------------------------ > > Key: JBDS-3070 > URL: https://issues.jboss.org/browse/JBDS-3070 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Fix For: LATER > > > since JBDS-3036 its become very obvious in the installer that the fonts are scrwed. > See http://screencast.com/t/ebR5zm1Cmmmw > On here is at least 3 or 4 different fonts. > Should use same clean fonts IMO -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:53:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 16 Oct 2015 13:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20978) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20978: ------------------------------------- Labels: application_wizard central connection_wizard openshift_v2 openshift_v3 (was: ) > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3087) Consider new installer packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3087: --------------------------------- Fix Version/s: LATER (was: 8.x) (was: 9.x) > Consider new installer packages > ------------------------------- > > Key: JBDS-3087 > URL: https://issues.jboss.org/browse/JBDS-3087 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Fix For: LATER > > > Today we have two installers: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > Both can be used for offline install, but both are large downloads. > When installing JBDS IS offline, a user must download several archives: > * JBDS installer jar (or update site zip) > * JBDS target platform zip > * JBDS IS zip > And, there's no "stub installer for online" which would simply fetch the content needed to do the install from the update site, making the installer a much smaller (initial) download footprint. > Therefore Max has suggested that we might want to add two new installers, resulting in this list: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > * Installer with Integration Stack (~750M) > * Stub Installer (~10M) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 13:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3087) Consider new installer packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3087: ------------------------------------ Assignee: Denis Golovin > Consider new installer packages > ------------------------------- > > Key: JBDS-3087 > URL: https://issues.jboss.org/browse/JBDS-3087 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: LATER > > > Today we have two installers: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > Both can be used for offline install, but both are large downloads. > When installing JBDS IS offline, a user must download several archives: > * JBDS installer jar (or update site zip) > * JBDS target platform zip > * JBDS IS zip > And, there's no "stub installer for online" which would simply fetch the content needed to do the install from the update site, making the installer a much smaller (initial) download footprint. > Therefore Max has suggested that we might want to add two new installers, resulting in this list: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > * Installer with Integration Stack (~750M) > * Stub Installer (~10M) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 13:56:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 16 Oct 2015 13:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20965) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Freemarker] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin closed JBIDE-20965. --------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Freemarker] > ------------------------------------------------------------ > > Key: JBIDE-20965 > URL: https://issues.jboss.org/browse/JBIDE-20965 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Freemarker]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22freemarker%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3093: ------------------------------------ Assignee: Nick Boldt (was: Max Rydahl Andersen) Was cleaning old JBDS issues and found this one. I honestly don't understand what this issue about. Do we currently miss anything that described in these A,B,C? > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3093: --------------------------------- Fix Version/s: LATER (was: 8.x) (was: 9.x) > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20979) Not able to resize the preferences window in JDBS 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20979: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20979 (was: JBDS-2499) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: upstream (was: upstream) Affects Version/s: 4.2.0.Final (was: 6.0.0.GA) (was: 8.0.0.Beta3) Fix Version/s: 4.4.x (was: 8.x) (was: 9.x) > Not able to resize the preferences window in JDBS 6 > --------------------------------------------------- > > Key: JBIDE-20979 > URL: https://issues.jboss.org/browse/JBIDE-20979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: Fedora 17, Fedora 19, > jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855 > Reporter: Sande Gilda > Assignee: Denis Golovin > Fix For: 4.4.x > > Attachments: JDBS6-01.png, JDBS6-02.png, JDBS6-03.png, JDBS6-04.png > > > To recreate: > Start JDBS. > Choose menu: Window --> Preferences > Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar. > When I hover over the edges, I get the arrow resize icon, but I can't resize it. > At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20979) Not able to resize the preferences window in JDBS 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20979: -------------------------------------- Assignee: Snjezana Peco (was: Denis Golovin) Another SWT issue. Assigning to [~snjeza] > Not able to resize the preferences window in JDBS 6 > --------------------------------------------------- > > Key: JBIDE-20979 > URL: https://issues.jboss.org/browse/JBIDE-20979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: Fedora 17, Fedora 19, > jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855 > Reporter: Sande Gilda > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JDBS6-01.png, JDBS6-02.png, JDBS6-03.png, JDBS6-04.png > > > To recreate: > Start JDBS. > Choose menu: Window --> Preferences > Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar. > When I hover over the edges, I get the arrow resize icon, but I can't resize it. > At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:11:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18667) Fixing SWT issues in Eclipse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-18667: ----------------------------------- Summary: Fixing SWT issues in Eclipse (was: Fixing SWT issues in Mars) > Fixing SWT issues in Eclipse > ---------------------------- > > Key: JBIDE-18667 > URL: https://issues.jboss.org/browse/JBIDE-18667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Jiri Peterka > Assignee: Snjezana Peco > Fix For: 4.3.x > > > Unresolved issues in Mars. > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431423 - [GTK3] [GTK3.8] Context menu should appear by pointer when invoked via mouse (https://issues.jboss.org/browse/JBIDE-16879) > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431425 - [GTK3] [GTK3.8] combo too small in vertical direction > https://bugs.eclipse.org/bugs/show_bug.cgi?id=434898 - [GTK3] vertical scrolling slow and lagging behind scrollwheel > https://bugs.eclipse.org/bugs/show_bug.cgi?id=465023 - Web Service Wizard drop-down layout issues in Mars on Fedora 20 (https://issues.jboss.org/browse/JBIDE-19638) > https://bugs.eclipse.org/bugs/show_bug.cgi?id=470516 - PopupMenuExtender.runCleanUp issue (https://issues.jboss.org/browse/JBIDE-20014) > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466099 - Not enough space for icons in Sapphire diagram title bar (https://issues.jboss.org/browse/JBIDE-20368) > The following issues have been fixed: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431421 - [GTK3] [GTK 3.8] Text outside of its area in vertical direction and residual text (https://issues.jboss.org/browse/JBIDE-16862) > https://bugs.eclipse.org/bugs/show_bug.cgi?id=446075 - Bug 446075 - [GTK3] [GTK 3.10] Garbled bold text when used with icons (https://issues.jboss.org/browse/JBIDE-19362) > https://bugs.eclipse.org/bugs/show_bug.cgi?id=438505 - [GTK3] Problem with table editing (https://issues.jboss.org/browse/JBIDE-17075) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:14:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 16 Oct 2015 14:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119188#comment-13119188 ] Denis Golovin commented on JBIDE-20609: --------------------------------------- On video EA connector installed, but after restart it looks like normal connector as installed not EA. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:15:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 16 Oct 2015 14:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119188#comment-13119188 ] Denis Golovin edited comment on JBIDE-20609 at 10/16/15 2:14 PM: ----------------------------------------------------------------- On video EA connector installed, but after restart it looks like normal connector was installed not EA. was (Author: dgolovin): On video EA connector installed, but after restart it looks like normal connector as installed not EA. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3122) Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3122: --------------------------------- Fix Version/s: 10.x (was: 8.x) > Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin > ------------------------------------------------------------------------------------------ > > Key: JBDS-3122 > URL: https://issues.jboss.org/browse/JBDS-3122 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: ui/branding > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Labels: f2f2014 > Fix For: 9.x, 10.x > > Attachments: fc20-mate-result.png, moonrise.png, moonrise_2.png, moonrise_3.png, moonrise_4.png, Screenshot-1.png, Screenshot-2.png, Screenshot-3.png, Screenshot.png > > > Based on stats and general crazy interests dark themes like provided by http://marketplace.eclipse.org/content/eclipse-moonrise-ui-theme and basic Eclipse Luna dark theme we should check if we have some obvious glitches when eclipse is switched to dark theme. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:24:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20980) Mobile Hybrid Project not opening on the emulator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20980: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20980 (was: JBDS-3454) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: aerogear-hybrid (was: aerogear-hybrid) Affects Version/s: 4.3.0.Alpha2 (was: 9.0.0.Alpha2) Fix Version/s: 4.4.x (was: 9.0.1.Beta1) > Mobile Hybrid Project not opening on the emulator > ------------------------------------------------- > > Key: JBIDE-20980 > URL: https://issues.jboss.org/browse/JBIDE-20980 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Supriya Bharadwaj > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.4.x > > Attachments: create_new_avd.png, error_project29july.log > > > I am trying to create a Mobile Hybrid project using the Mobile Hybrid Project wizard in JBoss Central. After its creation, the project does not open on the emulator. Also, if I export the project and try installing the apk file on a mobile android platform I get an "Application not installed" message. On certain environments (JBDS 9.0.0Alpha2 on RHEL 7) while trying to export the project it throws a "not an android project" error. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:26:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3516: ------------------------------------ Assignee: Misha Ali (was: Mickael Istria) > Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] > ------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3516 > URL: https://issues.jboss.org/browse/JBDS-3516 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, documentation, updatesite > Affects Versions: 9.0.0.CR1 > Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100 > jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0.0.CR1-updatesite-central.zip > Reporter: Jan Richter > Assignee: Misha Ali > Fix For: 9.0.1.Beta1 > > > This is what comes up when I try to install everything from the central zip: > {noformat} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:27:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 16 Oct 2015 14:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3535: --------------------------------- Target Release: (was: 9.1.0.GA) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:28:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 16 Oct 2015 14:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:28:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3535: --------------------------------- Status: New (was: New) Target Release: 9.0.1.GA > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:28:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 16 Oct 2015 14:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:28:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3535: --------------------------------- Target Release: (was: 9.0.1.GA) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:30:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 16 Oct 2015 14:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3535: ----------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:30:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3535: --------------------------------- Status: New (was: New) Target Release: 9.0.1.GA > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:30:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 16 Oct 2015 14:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3535: -------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:30:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3535: --------------------------------- > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:30:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBDS-3535. ---------------------------------- Resolution: Done > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.1.0.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:30:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3535) Installer progress looks bad with OS X El Capitan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3535: --------------------------------- Fix Version/s: 9.0.1.Beta1 (was: 9.1.0.Beta1) > Installer progress looks bad with OS X El Capitan > ------------------------------------------------- > > Key: JBDS-3535 > URL: https://issues.jboss.org/browse/JBDS-3535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.CR2 > Reporter: Martin Malina > Assignee: Daniel Azarov > Fix For: 9.0.1.Beta1 > > Attachments: install-progress.png > > > It seems that the progress bar in the installer changed its appearance in the new version of OS X 10.11 El Capitan (released Sep 30, 2015). > It is now a narrow stripe and the text that we display over it does not look nice. > !install-progress.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:31:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3539: --------------------------------- Fix Version/s: (was: 9.1.0.GA) > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui-scaling > Fix For: 9.0.1.Beta1, 10.0.0.Alpha1 > > Attachments: 4kInstaller.png, step2.png, step3.png, step4.png, step5.png, step6.png, step7.png, step8.png, step9.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:32:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3539) Installer UI does not scale on Windows (10) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3539: --------------------------------- Fix Version/s: 9.x (was: 9.0.1.Beta1) (was: 10.0.0.Alpha1) > Installer UI does not scale on Windows (10) > ------------------------------------------- > > Key: JBDS-3539 > URL: https://issues.jboss.org/browse/JBDS-3539 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.0.0.GA > Environment: Windows 10 > 9.0.0.GA installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui-scaling > Fix For: 9.x > > Attachments: 4kInstaller.png, step2.png, step3.png, step4.png, step5.png, step6.png, step7.png, step8.png, step9.png > > > I just tried to install JBDS on Windows 10 machine with 4K resolution. It's set to 250% scaling factor and the installer UI is still tiny. > Looks like this: > !4kInstaller.png|thumbnail! > Edit: Apparently some of the text does scale, so it doesn't even fit in the window sometimes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:36:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3496) AngularJS tooling is shown both with and without Early Access checked in Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBDS-3496. -------------------------------- Fix Version/s: 9.0.1.Beta1 (was: 9.x) Resolution: Duplicate Issue Will become irrelevant when we resolve JBIDE-20609 > AngularJS tooling is shown both with and without Early Access checked in Central > -------------------------------------------------------------------------------- > > Key: JBDS-3496 > URL: https://issues.jboss.org/browse/JBDS-3496 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, javascript > Affects Versions: 9.0.0.Beta2 > Reporter: Martin Malina > Assignee: Alexey Kazakov > Fix For: 9.0.1.Beta1 > > Attachments: angular-displayed.png > > > In the Software/Update tab of Central in JBDS 9.0.0.Beta2, I can see AngularJS for Web Tools even without checking "Enable Early Access". > AFAIK, AngularJS tooling should be early access only. > Once I check the early access checkbox, it will suddenly turn yellow marking it as early access. > This only happens in JBDS. In JBoss Tools, it is not displayed unless you check the early access checkbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20981) Creating bottom-up web service with a client result in error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20981: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20981 (was: JBDS-3461) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: webservices (was: webservices) Affects Version/s: 4.3.0.Beta2 (was: 9.0.0.Beta1) Fix Version/s: LATER (was: 9.x) > Creating bottom-up web service with a client result in error > ------------------------------------------------------------ > > Key: JBIDE-20981 > URL: https://issues.jboss.org/browse/JBIDE-20981 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Beta2 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Fix For: LATER > > > When creating a bottom-up web service along with a client using the web service wizard, it will create the service, but on the next step it throws an error saying: 'Selection must be WSDL.' > Note, this does not happen in Eclipse with JBT 4.3.0.Beta1. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3267) JSON Editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3267: --------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.x) > JSON Editor > ----------- > > Key: JBDS-3267 > URL: https://issues.jboss.org/browse/JBDS-3267 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing, requirements > Reporter: Burr Sutter > Assignee: Victor Rubezhny > Fix For: 10.0.0.Alpha1 > > > As a Java or Java EE developer, who wishes to test my JAX-RS endpoints as well as edit various JSON files, I need an editor that formats the nested curly braces, helps me to insure that I am not missing (nor have extra) curly braces, missing quotes, helps me to know when to use square brackets, etc. Ideally, the Eclipse Outline view would also work if I am editing a .json file. > Ideally, we would support both a full JSON editor as well as working within the Web Services Tester. > http://screencast.com/t/hWAtlMytghV6 > http://screencast.com/t/h4VWGyAuqw -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3267) JSON Editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3267: --------------------------------- Component/s: upstream > JSON Editor > ----------- > > Key: JBDS-3267 > URL: https://issues.jboss.org/browse/JBDS-3267 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing, requirements, upstream > Reporter: Burr Sutter > Assignee: Victor Rubezhny > Fix For: 10.0.0.Alpha1 > > > As a Java or Java EE developer, who wishes to test my JAX-RS endpoints as well as edit various JSON files, I need an editor that formats the nested curly braces, helps me to insure that I am not missing (nor have extra) curly braces, missing quotes, helps me to know when to use square brackets, etc. Ideally, the Eclipse Outline view would also work if I am editing a .json file. > Ideally, we would support both a full JSON editor as well as working within the Web Services Tester. > http://screencast.com/t/hWAtlMytghV6 > http://screencast.com/t/h4VWGyAuqw -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:42:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3267) JSON Editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119192#comment-13119192 ] Alexey Kazakov commented on JBDS-3267: -------------------------------------- We are currently working on contributing on a third party JSON editor (https://github.com/angelozerr/eclipse-wtp-json) to Eclipse SSE project. Targeting Eclipse Neon so far. > JSON Editor > ----------- > > Key: JBDS-3267 > URL: https://issues.jboss.org/browse/JBDS-3267 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing, requirements, upstream > Reporter: Burr Sutter > Assignee: Victor Rubezhny > Fix For: 10.0.0.Alpha1 > > > As a Java or Java EE developer, who wishes to test my JAX-RS endpoints as well as edit various JSON files, I need an editor that formats the nested curly braces, helps me to insure that I am not missing (nor have extra) curly braces, missing quotes, helps me to know when to use square brackets, etc. Ideally, the Eclipse Outline view would also work if I am editing a .json file. > Ideally, we would support both a full JSON editor as well as working within the Web Services Tester. > http://screencast.com/t/hWAtlMytghV6 > http://screencast.com/t/h4VWGyAuqw -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:44:00 2015 From: issues at jboss.org (Robert (Bob) Brodt (JIRA)) Date: Fri, 16 Oct 2015 14:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-470) BPEL plugins are not automatically updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119195#comment-13119195 ] Robert (Bob) Brodt commented on JBTIS-470: ------------------------------------------ I merged the PRs back in August, but apparently forgot to close this JIRA - sorry. > BPEL plugins are not automatically updated > ------------------------------------------ > > Key: JBTIS-470 > URL: https://issues.jboss.org/browse/JBTIS-470 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPEL, distribution > Affects Versions: 8.0.3.GA > Environment: JBDS-IS 8.0.3.CR2 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > BPEL plugins are not automatically updated. The problem is that the BPEL feature is still in version 1.3.100.Final-v20141204-2031-B13 but its feature.xml contains > {code:xml} > > > > {code} > which means that it installs any BPEL plugin compatible with 1.0.0. Note that during updating only feature version is considered, so in this case it is not automatically updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 14:45:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 14:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3514) Fix identified developer warning (OSX only) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3514: --------------------------------- Fix Version/s: LATER (was: 9.x) > Fix identified developer warning (OSX only) > ------------------------------------------- > > Key: JBDS-3514 > URL: https://issues.jboss.org/browse/JBDS-3514 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, installer, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Denis Golovin > Labels: new_and_noteworthy > Fix For: LATER > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014e0a14d9038d68677a2f4223e1a978447232b5f8b1e17cc58b989/jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar?_auth_=1414318523_22d0763be4332b55c325ef22cdff8386 > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 15:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 15:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119200#comment-13119200 ] Nick Boldt commented on JBIDE-20976: ------------------------------------ To help make the problems more visible (less scrolling), I've added a new comparator to sort the problems to the top of the HTML report: https://github.com/jbosstools/jbosstools-versionwatch/commit/9d7819dc526450da864da8183c4f827869dba331 Building: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/devstudio.versionwatch_master/lastBuild/console >= 2939 Output: http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 15:10:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 15:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Attachment: versionwatch-features.png versionwatch-plugins.png Success! [^versionwatch-features.png] [^versionwatch-plugins.png] Now, we just need to figure out why these IUs are backlevelled. :D > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 15:40:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 15:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3093: ----------------------------- Description: Max sais: {quote} This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. Thus lets discuss how far we are ok (in principle/not technical terms) early access goes A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? I assume YES because that is what the early access feature does that everyone was fine with before. B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) I assume YES since this has zero technical difference from A C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see But if you cannot even agree to it by principle then any technical discussion is pointless. Thus can you give Yes/No answers to the above please ? My answers are: A) Yes B) Yes C) Yes ...all with the assumption we make it clear that once you do this you are running in "early access" mode. For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". {quote} was: This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. Thus lets discuss how far we are ok (in principle/not technical terms) early access goes A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? I assume YES because that is what the early access feature does that everyone was fine with before. B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) I assume YES since this has zero technical difference from A C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see But if you cannot even agree to it by principle then any technical discussion is pointless. Thus can you give Yes/No answers to the above please ? My answers are: A) Yes B) Yes C) Yes ...all with the assumption we make it clear that once you do this you are running in "early access" mode. For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > Max sais: > {quote} > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 15:40:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 15:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3093: ----------------------------- Description: Max said: {quote} This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. Thus lets discuss how far we are ok (in principle/not technical terms) early access goes A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? I assume YES because that is what the early access feature does that everyone was fine with before. B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) I assume YES since this has zero technical difference from A C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see But if you cannot even agree to it by principle then any technical discussion is pointless. Thus can you give Yes/No answers to the above please ? My answers are: A) Yes B) Yes C) Yes ...all with the assumption we make it clear that once you do this you are running in "early access" mode. For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". {quote} was: Max sais: {quote} This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. Thus lets discuss how far we are ok (in principle/not technical terms) early access goes A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? I assume YES because that is what the early access feature does that everyone was fine with before. B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) I assume YES since this has zero technical difference from A C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see But if you cannot even agree to it by principle then any technical discussion is pointless. Thus can you give Yes/No answers to the above please ? My answers are: A) Yes B) Yes C) Yes ...all with the assumption we make it clear that once you do this you are running in "early access" mode. For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". {quote} > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > Max said: > {quote} > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 15:46:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 16 Oct 2015 15:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119210#comment-13119210 ] Nick Boldt commented on JBDS-3093: ---------------------------------- To achieve the option to "roll back" something between JBDS 9 and 9.x, we need, simply, an update site with both the latest and previous versions on it. We have in the past debated the performance impact of an update site which composites 8.0.0, 8.0.1, 8.1.0, etc. in the same site and it was decided IIRC NOT to do that because of the performance hit for new users. That said, if this issue is simply about having a composite site of old / current EARLY ACCESS bits, we can totally do that with minimal performance hit for two reasons: * EA is a tiny site, especially compared to the (JBDS + JBDS TP + JBDS Central) site * EA is already subject to "this might break your machine" warnings, so making it a bit slower to install/rollback shouldn't be a big deal IMHO. So, if we want this for 9.x, we can add some instructions to the release guide for JBT/JBDS/JBTIS/JBDSIS to clarify that new EA releases should simply be ADDED to the /earlyaccess/ URLs, rather than replacing them. OTOH, since this issue is over 1 year old, we could just close it as WONTFIX. > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > Max said: > {quote} > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 15:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 15:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3328) generate/edit jboss modules content for easily deployment/config of jdbc driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3328: --------------------------------- Fix Version/s: 10.x (was: 9.x) > generate/edit jboss modules content for easily deployment/config of jdbc driver > ------------------------------------------------------------------------------- > > Key: JBDS-3328 > URL: https://issues.jboss.org/browse/JBDS-3328 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Viacheslav Kabanovich > Fix For: 10.x > > > in EAP7-56 its asked: > "I can easily generate and deploy a JBoss Module from existing jars including JDBC Drivers and shared libraries. (Tooling to automatically generate module.xml and related artifacts by scanning classes from a library jar file, or pom.xml if provided e.g real life use case: creating modules for JDBC Type 4 Drivers )" > this would be nice to have and linked with our datasource wizards. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 15:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 15:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1991) Migrate IzPack Installer Build to maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-1991: --------------------------------- Fix Version/s: LATER (was: 9.x) > Migrate IzPack Installer Build to maven > --------------------------------------- > > Key: JBDS-1991 > URL: https://issues.jboss.org/browse/JBDS-1991 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer > Affects Versions: 5.0.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: LATER > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:00:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2564) JBDS70_1214: [Commit] (?) (P?) Fix OpenShift support for multi-module maven projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-2564: ------------------------------------ Assignee: Andre Dietisheim > JBDS70_1214: [Commit] (?) (P?) Fix OpenShift support for multi-module maven projects > ------------------------------------------------------------------------------------ > > Key: JBDS-2564 > URL: https://issues.jboss.org/browse/JBDS-2564 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Fix For: 9.x > > > Could be better at detecting proper packaging type for the openshift profile. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:02:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20982) JBDS consumes 40-50% CPU without any noticeable job in progress In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20982: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20982 (was: JBDS-3147) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: upstream (was: upstream) Affects Version/s: 4.2.0.Final (was: 8.0.0.CR1) Fix Version/s: 4.4.x (was: 9.x) > JBDS consumes 40-50% CPU without any noticeable job in progress > --------------------------------------------------------------- > > Key: JBIDE-20982 > URL: https://issues.jboss.org/browse/JBIDE-20982 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Fix For: 4.4.x > > Attachments: jstack-JBDS-3147-1.txt, jstack-JBDS-3147-2.txt, jstack-JBDS-3147-3.txt, jstack-JBDS-3147-4.txt, Screen Shot 2014-09-11 at 16.06.20.png, Screen Shot 2014-09-12 at 09.22.31.png, Screen Shot 2014-09-12 at 12.33.40.png, Screen Shot 2014-09-12 at 17.49.48.png > > > Steps to reproduce (on MacOSX): > - import all WildFly Quickstarts (https://github.com/wildfly/quickstart) > - restart the workbench > - once all projects have been built and no job appears in the progress view, JBDS still consumes ~40% a CPU -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20982) JBDS consumes 40-50% CPU without any noticeable job in progress In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20982: -------------------------------------- Assignee: Snjezana Peco One more SWT issue. > JBDS consumes 40-50% CPU without any noticeable job in progress > --------------------------------------------------------------- > > Key: JBIDE-20982 > URL: https://issues.jboss.org/browse/JBIDE-20982 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: jstack-JBDS-3147-1.txt, jstack-JBDS-3147-2.txt, jstack-JBDS-3147-3.txt, jstack-JBDS-3147-4.txt, Screen Shot 2014-09-11 at 16.06.20.png, Screen Shot 2014-09-12 at 09.22.31.png, Screen Shot 2014-09-12 at 12.33.40.png, Screen Shot 2014-09-12 at 17.49.48.png > > > Steps to reproduce (on MacOSX): > - import all WildFly Quickstarts (https://github.com/wildfly/quickstart) > - restart the workbench > - once all projects have been built and no job appears in the progress view, JBDS still consumes ~40% a CPU -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20983) cannot use oracle service name in datasource creation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20983: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20983 (was: JBDS-3403) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: upstream (was: runtime) Affects Version/s: 4.2.2.Final (was: 8.0.2.GA) Fix Version/s: 4.4.x (was: 9.x) > cannot use oracle service name in datasource creation > ----------------------------------------------------- > > Key: JBIDE-20983 > URL: https://issues.jboss.org/browse/JBIDE-20983 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.2.Final > Reporter: Tom Fonteyne > Fix For: 4.4.x > > > When connecting to an Oracle data source, a SID is required for a connection and a service name can not be used. > The Oracle URL formats are: > With a SID you use ":sid" at the end > jdbc:oracle:thin:@//oraclehost:1521:mysid > with a service name you use "/myservicename" > jdbc:oracle:thin:@//oraclehost:1521/myservicename > The dialog box prevent removing the ":" and replacing it with the needed "/" > (not even via the driver definition where you seem to be allowed to set the url format...) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20983) cannot use oracle service name in datasource creation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20983: -------------------------------------- Assignee: Koen Aers > cannot use oracle service name in datasource creation > ----------------------------------------------------- > > Key: JBIDE-20983 > URL: https://issues.jboss.org/browse/JBIDE-20983 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.2.Final > Reporter: Tom Fonteyne > Assignee: Koen Aers > Fix For: 4.4.x > > > When connecting to an Oracle data source, a SID is required for a connection and a service name can not be used. > The Oracle URL formats are: > With a SID you use ":sid" at the end > jdbc:oracle:thin:@//oraclehost:1521:mysid > with a service name you use "/myservicename" > jdbc:oracle:thin:@//oraclehost:1521/myservicename > The dialog box prevent removing the ":" and replacing it with the needed "/" > (not even via the driver definition where you seem to be allowed to set the url format...) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:11:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3193) JBDS 8 generates .attach_pid* file if IDE is started with a new workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3193: ------------------------------------ Assignee: Denis Golovin > JBDS 8 generates .attach_pid* file if IDE is started with a new workspace > ------------------------------------------------------------------------- > > Key: JBDS-3193 > URL: https://issues.jboss.org/browse/JBDS-3193 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 8.0.0.GA > Environment: Fedora 20 x86_64 + Java 1.8.0_20 + JBDS 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Denis Golovin > Priority: Minor > Labels: fedora, java8 > Fix For: LATER > > > JBDS 8 always generates .attach_pidXXXX. The file is empty and it is generated in the folder from where you executed the JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:11:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3193) JBDS 8 generates .attach_pid* file if IDE is started with a new workspace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3193: --------------------------------- Fix Version/s: LATER (was: 9.x) > JBDS 8 generates .attach_pid* file if IDE is started with a new workspace > ------------------------------------------------------------------------- > > Key: JBDS-3193 > URL: https://issues.jboss.org/browse/JBDS-3193 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 8.0.0.GA > Environment: Fedora 20 x86_64 + Java 1.8.0_20 + JBDS 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Denis Golovin > Priority: Minor > Labels: fedora, java8 > Fix For: LATER > > > JBDS 8 always generates .attach_pidXXXX. The file is empty and it is generated in the folder from where you executed the JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:12:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3456) Resizing JBDS window right after is appears crashes it with GTK3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3456: --------------------------------- Component/s: (was: ui/branding) > Resizing JBDS window right after is appears crashes it with GTK3 > ---------------------------------------------------------------- > > Key: JBDS-3456 > URL: https://issues.jboss.org/browse/JBDS-3456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Snjezana Peco > Fix For: 9.x > > Attachments: core_backtrace > > > If I try to resize/maximize the JBDS window right after launch, it crashes when the window has not finished rendering before the resize. There is no error in the log, just Fedora telling me that the JVM crashed. Running with GTK2 doesn't produce this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2625) Provide on-line installer launchable via JNLP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-2625: --------------------------------- Fix Version/s: LATER (was: 9.x) > Provide on-line installer launchable via JNLP > --------------------------------------------- > > Key: JBDS-2625 > URL: https://issues.jboss.org/browse/JBDS-2625 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: LATER > > > Instead of always downloading offline installer and then run installation manually, would be good to have online version of installer that would let: > # start installer via JNLP > # select if EAP/WildFly should be installed too > (1) Should be easy to implement, because it requires only excluding update site bits from jar, provide URL for update site and create JNLP configuration; > (2) Requires EAP download integration into IzPack (would be good if IzPack has supported online installation itself) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3396) Online installer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3396: --------------------------------- Fix Version/s: LATER (was: 9.x) > Online installer > ----------------- > > Key: JBDS-3396 > URL: https://issues.jboss.org/browse/JBDS-3396 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: LATER > > > Online installer would contains only p2 director and install JBDS product from remote p2 repository -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:19:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20984) Arquillian Cruiser view is in default JBDS installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20984: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20984 (was: JBDS-3419) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: arquillian upstream (was: upstream) (was: arquillian) Affects Version/s: 4.3.0.Final (was: 9.0.0.Alpha2) Fix Version/s: 4.4.x (was: 9.x) > Arquillian Cruiser view is in default JBDS installation > ------------------------------------------------------- > > Key: JBIDE-20984 > URL: https://issues.jboss.org/browse/JBIDE-20984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, upstream > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBoss - JBoss Central - JBoss Developer Studio _001.png > > > Default JBDS installation contains "Arquillia Cruiser" (missing n) view. Arquillian from central isn't installed. View is missing icon and does not work at all - if you try to open it you will get view with "Could not create the view: org.jboss.tools.arquillian.ui.views.arquillianView" text. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:22:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3174) Support Latest JavaScript standard - ECMA-262 5th Edition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3174: --------------------------------- Fix Version/s: 10.x (was: 9.x) > Support Latest JavaScript standard - ECMA-262 5th Edition > --------------------------------------------------------- > > Key: JBDS-3174 > URL: https://issues.jboss.org/browse/JBDS-3174 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, visual-page-editor-core > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:22:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3174) Support Latest JavaScript standard - ECMA-262 5th Edition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3174: --------------------------------- Component/s: (was: visual-page-editor-core) (was: aerogear-hybrid) > Support Latest JavaScript standard - ECMA-262 5th Edition > --------------------------------------------------------- > > Key: JBDS-3174 > URL: https://issues.jboss.org/browse/JBDS-3174 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: jsp/jsf/xml/html-source-editing > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:22:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3174) Support Latest JavaScript standard - ECMA-262 5th Edition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3174: ------------------------------------ Assignee: Victor Rubezhny (was: Denis Golovin) > Support Latest JavaScript standard - ECMA-262 5th Edition > --------------------------------------------------------- > > Key: JBDS-3174 > URL: https://issues.jboss.org/browse/JBDS-3174 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, visual-page-editor-core > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3174) Support Latest JavaScript standard - ECMA-262 5th Edition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3174: --------------------------------- Component/s: javascript (was: jsp/jsf/xml/html-source-editing) > Support Latest JavaScript standard - ECMA-262 5th Edition > --------------------------------------------------------- > > Key: JBDS-3174 > URL: https://issues.jboss.org/browse/JBDS-3174 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: javascript > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3492: --------------------------------- Fix Version/s: LATER (was: 9.x) > JBDS app icon and installer icon are not the same > ------------------------------------------------- > > Key: JBDS-3492 > URL: https://issues.jboss.org/browse/JBDS-3492 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta2 > Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png > > > The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it. > Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app. > This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually. > Screenshot showing an installer dialog superimposed over JBDS: > !jbds-installer-vs-installer-jbds-icon.png! > Should we change this? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16974) 'Syntax error on token "continue", Identifier expected' when Adding Cordova Contacts plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-16974: ----------------------------------- Component/s: javascript (was: jsp/jsf/xml/html-source-editing) > 'Syntax error on token "continue", Identifier expected' when Adding Cordova Contacts plugin > ------------------------------------------------------------------------------------------- > > Key: JBIDE-16974 > URL: https://issues.jboss.org/browse/JBIDE-16974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Reporter: Burr Sutter > Assignee: Victor Rubezhny > Fix For: 4.3.x > > > Adding the org.apache.cordova.contacts plugin gives me the following error in JBDS8 (about Beta 1) > http://screencast.com/t/XH8Q6HbL -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:24:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3492: ------------------------------------ Assignee: Denis Golovin (was: Nick Boldt) > JBDS app icon and installer icon are not the same > ------------------------------------------------- > > Key: JBDS-3492 > URL: https://issues.jboss.org/browse/JBDS-3492 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta2 > Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Optional > Fix For: LATER > > Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png > > > The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it. > Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app. > This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually. > Screenshot showing an installer dialog superimposed over JBDS: > !jbds-installer-vs-installer-jbds-icon.png! > Should we change this? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2065) Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-2065: --------------------------------- Fix Version/s: LATER (was: 9.x) > Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE > ----------------------------------------------------------------------------------- > > Key: JBDS-2065 > URL: https://issues.jboss.org/browse/JBDS-2065 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 5.0.0.M5 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: LATER > > Attachments: Screen Shot 2012-03-09 at 10.05.17.jpg > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-2260: --------------------------------- Fix Version/s: LATER (was: 9.x) > Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-2260 > URL: https://issues.jboss.org/browse/JBDS-2260 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.GA > Reporter: Isaac Rooskov > Assignee: Denis Golovin > Fix For: LATER > > Attachments: JavaVersionReader.java.patch > > > *From customer in Bugzilla* > Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793 > Description of issue from customer: > Description of problem: > Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4 > Version-Release number of selected component (if applicable): > JBOSS Developer Studio 5.0.0.GA > How reproducible: > Start installation using > java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar > Actual results: > Installation is not passing at step 7 of 9, progress 1 of 4. > Expected results: > Additional info: -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1609) Installer should check system prerequisites and warn user if they are not fullfilled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-1609: --------------------------------- Fix Version/s: LATER (was: 9.x) > Installer should check system prerequisites and warn user if they are not fullfilled > ------------------------------------------------------------------------------------ > > Key: JBDS-1609 > URL: https://issues.jboss.org/browse/JBDS-1609 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Minor > Fix For: LATER > > > To prevent insufficient machine parameters or setting installer should do basic check for some parameters like: > - memory amount > - maximum open file limit > - maximum thread count limit > - internet connection > - others reasonable criteria should be added here > If these criteria aren't met, installer should display add warning page before further installation saying that requirements aren't satisfied and tools may not work properly. Reason for this is that sometimes JBDS is used in very strict environment (typically training rooms, universities, etc where many system resources are limited or blocked) but user isn't warned and after install user can see after that lots of runtime errors and got bad feeling about the tool. This should be avoided and user should be at least warn that he is running JBDS in inappropriate environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:29:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-1504) allow users to create cases from JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-1504: --------------------------------- Fix Version/s: (was: 9.x) > allow users to create cases from JBDS > ------------------------------------- > > Key: JBDS-1504 > URL: https://issues.jboss.org/browse/JBDS-1504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: integration > Environment: All > Reporter: Andrew Hecox > Assignee: Max Rydahl Andersen > Fix For: LATER > > > user-story: as a JBoss customer, I can create a case with support from JBDS so that I can easily get help solving the problem I'm working on in my editor > notes: I think something which allowed a user to create a problem description, as well as send any applicable files, would be a good value add to JBDS. We have a public, stable, API for this: > https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/ > we may deprecate some schema items in the next month or two, but otherwise it's locked in place for the next 7+ years. This functionality presumably would only be in the productized version, unless it was replaced with JIRA integration (or comparable) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:30:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 16 Oct 2015 16:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20985) XML Schema validation fails when importing external schema In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20985: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20985 (was: JBDS-3119) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: upstream (was: 3rd-party-dependencies) (was: server) Affects Version/s: 4.2.3.Final (was: 8.0.0.Beta3) Fix Version/s: 4.3.x (was: 10.0.0.GA) (was: 9.1.0.GA) (was: 9.0.1.Beta1) > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBIDE-20985 > URL: https://issues.jboss.org/browse/JBIDE-20985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.3.Final > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.x > > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 16:54:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 16 Oct 2015 16:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119222#comment-13119222 ] Paul Leacu commented on JBDS-3276: ---------------------------------- Okay - now that there's a 9.0.0.Alpha2 JBDSIS release, it's time to resurrect the conversation on a standalone JBDSIS installer. For DEMONSTRATION PURPOSES ONLY - i have the following for your consideration: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar This installer contains EARLY ACCESS plugins - basically because everything of interest in the integration stack is early access. In addition, the usability people like [~crobson] have asked for even more specific tweeks to the installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration {code} The PM management team has asked for a further refinement to the JBDSIS standalone installer where the jbdevstudio default perspective is set to the Fuse Integration perspective by default. That's a little more complicated to happen and wanted to get initial reaction from the people on the watch list of this Jira and Catherine. WDYT??? > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, mirroringlog.txt > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 17:34:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 17:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized In-Reply-To: References: Message-ID: Fred Bricon created JBIDE-20986: ----------------------------------- Summary: JBoss EAP 7 Maven repository is not recognized Key: JBIDE-20986 URL: https://issues.jboss.org/browse/JBIDE-20986 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.3.0.Final Reporter: Fred Bricon - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) - ASSERT the Maven repo should be recognized as an EAP repo - FAILURE a "No new repository found" message is displayed This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 17:38:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 17:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20986: -------------------------------- Fix Version/s: 4.3.1.Beta1 > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Fix For: 4.3.1.Beta1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 16 17:38:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 16 Oct 2015 17:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20986: ----------------------------------- Assignee: Fred Bricon > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:31:01 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 04:31:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3538: -------------------------------------- Status: New (was: New) > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:31:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Mon, 19 Oct 2015 04:31:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3538: ----------------------------- > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA, 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:31:02 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 04:31:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3538: -------------------------------------- Target Release: 9.0.0.GA (was: 9.1.0.GA) > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA, 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:31:03 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 04:31:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3538: -------------------------------------- Fix Version/s: 9.0.0.GA > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA, 9.0.1.Beta1 > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:32:01 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 04:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3538: -------------------------------------- Fix Version/s: (was: 9.0.1.Beta1) > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:32:01 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 04:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3538: -------------------------------------- Status: New (was: New) > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:32:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Mon, 19 Oct 2015 04:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3538: -------------------------------- > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:32:02 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 04:32:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3538: -------------------------------------- > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:33:01 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 04:33:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen resolved JBDS-3538. --------------------------------------- Resolution: Done It was found that one of the jars were corrupt on some servers in akamai. The bad file have been purged and we should be back to normal. If you still see problems please open new issue with details and link/mention this issue. Thank you! > read timeouts accessing JBDS discovery bits (possible Akamai problem?) > ---------------------------------------------------------------------- > > Key: JBDS-3538 > URL: https://issues.jboss.org/browse/JBDS-3538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.GA > > > As reported in JBDS-3525: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289 > !MESSAGE Cannot download bundle at > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/com.jboss.jbds.central.discovery_9.0.0.Final-v20151003-0935-B142.jar: > Read timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593) > at sun.security.ssl.InputRecord.read(InputRecord.java:532) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198) > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700 > !MESSAGE Unexpected error > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > 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.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 13 more{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 05:05:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 19 Oct 2015 05:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117320#comment-13117320 ] Supriya Bharadwaj edited comment on TOOLSDOC-307 at 10/19/15 5:04 AM: ---------------------------------------------------------------------- > Discussion with Marian about change in this functionality > Tried out steps as he had suggested >> Created new ssh key >> Created project on https://openshift.redhat.com >> Trying to import the project into jbds; unable to do so; getting an error: "failed to read artifact description" was (Author: supriya.bharadwaj): > Discussion with Marian about change in this functionality > Tried out steps as per he had suggested >> Created new ssh key >> Created project on https://openshift.redhat.com >> Trying to import the project into jbds; unable to do so; getting an error: "failed to read artifact description" > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 05:52:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 05:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119347#comment-13119347 ] Max Rydahl Andersen commented on JBDS-3093: ------------------------------------------- I completely disagree on doing this for earlyaccess but not for JBDS core. That just don't make sense to me. Earlyaccess if anything would be reliant on also being able to rollback to the exact matching JBDS core version it been tested with. Earlyaccess is not at all a tiny site when you include that integrationstack is in there for periods of time. [~akazakov] I'm fine closing this issue since it is not covering the actual problem that we do need to look at: how to handle multiple releases at different release schedules of our eclipse features - today we have jbds core vs IS at different times; what happens when we add more into this. Then we can't just install all of JBDS all the time. > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > Max said: > {quote} > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 05:54:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 05:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119348#comment-13119348 ] Max Rydahl Andersen commented on JBDS-3093: ------------------------------------------- to be clear, this issue is a no-op for me - earlyaccess was designed to allow earlyaccess to JBDS core features. Not just for addons. i.e. JBDS 9.1 could *potentially* be offered as EarlyAccess if we verify it works with existing IS at the time of release. > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > Max said: > {quote} > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 06:02:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 19 Oct 2015 06:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20978) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20978: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. was: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: connection page shows up as 1st wizard page # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 06:21:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 06:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119347#comment-13119347 ] Max Rydahl Andersen edited comment on JBDS-3093 at 10/19/15 6:20 AM: --------------------------------------------------------------------- I completely disagree on adding support for restoring for earlyaccess but not for JBDS core. That just don't make sense to me. Earlyaccess if anything would be reliant on also being able to rollback to the exact matching JBDS core version it been tested with. Earlyaccess is not at all a tiny site when you include that integrationstack is in there for periods of time. [~akazakov] I'm fine closing this issue since it is not covering the actual problem that we do need to look at: how to handle multiple releases at different release schedules of our eclipse features - today we have jbds core vs IS at different times; what happens when we add more into this. Then we can't just install all of JBDS all the time. was (Author: maxandersen): I completely disagree on doing this for earlyaccess but not for JBDS core. That just don't make sense to me. Earlyaccess if anything would be reliant on also being able to rollback to the exact matching JBDS core version it been tested with. Earlyaccess is not at all a tiny site when you include that integrationstack is in there for periods of time. [~akazakov] I'm fine closing this issue since it is not covering the actual problem that we do need to look at: how to handle multiple releases at different release schedules of our eclipse features - today we have jbds core vs IS at different times; what happens when we add more into this. Then we can't just install all of JBDS all the time. > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > Max said: > {quote} > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 07:22:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 07:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119376#comment-13119376 ] Max Rydahl Andersen commented on JBIDE-19178: --------------------------------------------- [~hardy.ferentschik] if you are being switched to another tab then rearrange your views ;) I have the properties view in the lower left while server view is on the right in the middle. That means the properties view never moves and I can 'inline' edit all values no matter which part of eclipse i'm in. truly "inlining" the properties into the tree I think will be too much overload on normal users screens. > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 07:51:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 07:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119392#comment-13119392 ] Max Rydahl Andersen commented on JBIDE-20976: --------------------------------------------- also need to figure out why QE greenlighted the release without this check. Was it not run or was it giving false results before ? > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 07:52:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 07:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119394#comment-13119394 ] Max Rydahl Andersen commented on JBIDE-20976: --------------------------------------------- never mind, I read it as JBDS 8 to 9. so yeah, good question why/how they could even backlevel at the plain TP level. > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:18:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 19 Oct 2015 08:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119411#comment-13119411 ] Martin Malina commented on TOOLSDOC-687: ---------------------------------------- Hi [~mhusnain], I guess I forgot to reply to your update. I checked the live version of the JBDS 9.0.0.GA version of Release Notes now and it seems that the fixes are contained there, so this JIRA can be resolved. > Review JBDS 9 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-687 > URL: https://issues.jboss.org/browse/TOOLSDOC-687 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Reporter: Misha Ali > Assignee: Misha Ali > > Please review here: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:19:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 19 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina resolved TOOLSDOC-687. ------------------------------------ Fix Version/s: 4.3.0.Final Resolution: Done Done. > Review JBDS 9 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-687 > URL: https://issues.jboss.org/browse/TOOLSDOC-687 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > Please review here: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:19:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Mon, 19 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed TOOLSDOC-687. ---------------------------------- Verified. > Review JBDS 9 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-687 > URL: https://issues.jboss.org/browse/TOOLSDOC-687 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > Please review here: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:30:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Mon, 19 Oct 2015 08:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-513) JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-513. ----------------------------------- Verified with JBDS-IS 8.0.4.CR2 > JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie > ---------------------------------------------------------------- > > Key: JBTIS-513 > URL: https://issues.jboss.org/browse/JBTIS-513 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, drools/ jBPM > Affects Versions: 8.0.4.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.4.CR2, 4.2.4.CR2 > > > At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see that there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:55:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Mon, 19 Oct 2015 08:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20987) Project combo not populated regression In-Reply-To: References: Message-ID: Jeff Cantrill created JBIDE-20987: ------------------------------------- Summary: Project combo not populated regression Key: JBIDE-20987 URL: https://issues.jboss.org/browse/JBIDE-20987 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Fix For: 4.3.1.Beta1 Projects not correctly populated after fix to JBIDE-20714 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:55:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 19 Oct 2015 08:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20988) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: Ilya Buziuk created JBIDE-20988: ----------------------------------- Summary: Preference validation fails on windows if node executable called node64.exe Key: JBIDE-20988 URL: https://issues.jboss.org/browse/JBIDE-20988 Project: Tools (JBoss Tools) Issue Type: Bug Components: javascript, javascript-bower Affects Versions: 4.3.0.Final Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:55:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Mon, 19 Oct 2015 08:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20987) Project combo not populated regression In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill resolved JBIDE-20987. ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) Resolution: Done Cherry-picked into master: 1f61ce57437023b65629c64e392030236757c1b5 > Project combo not populated regression > -------------------------------------- > > Key: JBIDE-20987 > URL: https://issues.jboss.org/browse/JBIDE-20987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > > Projects not correctly populated after fix to JBIDE-20714 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:59:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 19 Oct 2015 08:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20988) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20988: -------------------------------- Description: For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). Node preference validation fails for 64-bit version. > Preference validation fails on windows if node executable called node64.exe > --------------------------------------------------------------------------- > > Key: JBIDE-20988 > URL: https://issues.jboss.org/browse/JBIDE-20988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). > Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:00:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 19 Oct 2015 09:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20989) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: Ilya Buziuk created JBIDE-20989: ----------------------------------- Summary: Preference validation fails on windows if node executable called node64.exe Key: JBIDE-20989 URL: https://issues.jboss.org/browse/JBIDE-20989 Project: Tools (JBoss Tools) Issue Type: Bug Components: javascript, javascript-bower Affects Versions: 4.3.0.Final Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.4.0.Alpha1 For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:00:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 19 Oct 2015 09:00:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20989) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20989: -------------------------------- Fix Version/s: 4.3.1.Final (was: 4.4.0.Alpha1) > Preference validation fails on windows if node executable called node64.exe > --------------------------------------------------------------------------- > > Key: JBIDE-20989 > URL: https://issues.jboss.org/browse/JBIDE-20989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). > Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:00:01 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 09:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBDS-3276: ----------------------------- Attachment: sai1.png > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:03:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Mon, 19 Oct 2015 09:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20989) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20989: -------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.1.Final) > Preference validation fails on windows if node executable called node64.exe > --------------------------------------------------------------------------- > > Key: JBIDE-20989 > URL: https://issues.jboss.org/browse/JBIDE-20989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Beta1 > > > For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). > Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:06:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 09:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119222#comment-13119222 ] Paul Leacu edited comment on JBDS-3276 at 10/19/15 9:05 AM: ------------------------------------------------------------ [~maxandersen] [~burrsutter] [~ldimaggio] Okay - now that there's a 9.0.0 JBDSIS release, it's time to resurrect the conversation on a standalone JBDSIS installer. For DEMONSTRATION PURPOSES ONLY - I have the following for your consideration: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar This installer contains EARLY ACCESS plugins - basically because everything of interest in the integration stack is early access. In addition, the usability people like [~crobson] have asked for even more specific tweeks to the installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration {code} The PM management team has asked for a further refinement to the JBDSIS standalone installer where the jbdevstudio default perspective is set to the Fuse Integration perspective by default. That's a little more complicated to happen and wanted to get initial reaction from the people on the watch list of this Jira and Catherine. WDYT??? was (Author: pleacu): Okay - now that there's a 9.0.0.Alpha2 JBDSIS release, it's time to resurrect the conversation on a standalone JBDSIS installer. For DEMONSTRATION PURPOSES ONLY - i have the following for your consideration: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar This installer contains EARLY ACCESS plugins - basically because everything of interest in the integration stack is early access. In addition, the usability people like [~crobson] have asked for even more specific tweeks to the installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration {code} The PM management team has asked for a further refinement to the JBDSIS standalone installer where the jbdevstudio default perspective is set to the Fuse Integration perspective by default. That's a little more complicated to happen and wanted to get initial reaction from the people on the watch list of this Jira and Catherine. WDYT??? > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:09:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 09:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119440#comment-13119440 ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- thanks! downloadin and trying out the installer now. About "PM Management team" - who/what is that in this case ? About handling/showing different perspectives then I honestly think that is for a separate issue since most will not use the installer to install the tooling; BYOE is the majority for now. Also, if we only make this combined installer available then Fuse is not the sensible thing to show. but what is it in the Fuse perspective that is not working for them with the JBoss perspective ? Maybe we can fix that instead of just falling back to Fuse by default ? Also, fixing the default perspective does not fix that JBoss Central will still show up and not have Fuse as the first thing to choose. My understanding this comes down to how different users install and use our plugins. This is what we in past have discussed as having a way a preference to let users define what their persona/interest are and have that reflected in not only what perspective is default but what happens in JBoss Central. so in short - I think this topic about how to handle startup perspective etc. is for a separate issue. > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:41:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 09:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-20990: ------------------------------------------- Summary: Add "CDK Server" for start/stop for the CDK Key: JBIDE-20990 URL: https://issues.jboss.org/browse/JBIDE-20990 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Reporter: Max Rydahl Andersen We want to be able to start/stop CDK easily. Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:47:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 09:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-20991: ------------------------------------------- Summary: support automatic setup of CDK start/stop server Key: JBIDE-20991 URL: https://issues.jboss.org/browse/JBIDE-20991 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection Reporter: Max Rydahl Andersen related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:48:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 09:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119475#comment-13119475 ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- In way how this works the LiveReload server seems like a good approach. Has a command that can be run to start/stop the server no matter if there is a server to start with. Would be great we would have similar for CDK (we would need to ask the user for the CDK install though). > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:53:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 09:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Comment: was deleted (was: also need to figure out why QE greenlighted the release without this check. Was it not run or was it giving false results before ?) > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:53:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 09:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Comment: was deleted (was: never mind, I read it as JBDS 8 to 9. so yeah, good question why/how they could even backlevel at the plain TP level.) > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:54:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 09:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119481#comment-13119481 ] Nick Boldt commented on JBIDE-20976: ------------------------------------ (Two comments deleted because they contribute nothing to this thread. See "All" tab if you need to review them.) > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:56:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 09:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3546) Update 4.3.0.Final composites In-Reply-To: References: Message-ID: Paul Leacu created JBDS-3546: -------------------------------- Summary: Update 4.3.0.Final composites Key: JBDS-3546 URL: https://issues.jboss.org/browse/JBDS-3546 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Reporter: Paul Leacu Assignee: Paul Leacu The IS is now at 9.0.0.GA/ 4.3.0.Final - update the community side. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:58:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 09:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20984) Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20984: ------------------------------- Summary: Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects (was: Arquillian Cruiser view is in default JBDS installation) > Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20984 > URL: https://issues.jboss.org/browse/JBIDE-20984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, upstream > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBoss - JBoss Central - JBoss Developer Studio _001.png > > > Default JBDS installation contains "Arquillia Cruiser" (missing n) view. Arquillian from central isn't installed. View is missing icon and does not work at all - if you try to open it you will get view with "Could not create the view: org.jboss.tools.arquillian.ui.views.arquillianView" text. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:58:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 09:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20984) Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119485#comment-13119485 ] Nick Boldt commented on JBIDE-20984: ------------------------------------ [~snjeza] Did you report this upstream to Platform UI? > Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20984 > URL: https://issues.jboss.org/browse/JBIDE-20984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, upstream > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBoss - JBoss Central - JBoss Developer Studio _001.png > > > Default JBDS installation contains "Arquillia Cruiser" (missing n) view. Arquillian from central isn't installed. View is missing icon and does not work at all - if you try to open it you will get view with "Could not create the view: org.jboss.tools.arquillian.ui.views.arquillianView" text. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:59:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 09:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-522) Update 4.3.0.Final composites In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-522: ----------------------------- Project: JBoss Tools Integration Stack (was: Developer Studio (JBoss Developer Studio)) Key: JBTIS-522 (was: JBDS-3546) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) > Update 4.3.0.Final composites > ----------------------------- > > Key: JBTIS-522 > URL: https://issues.jboss.org/browse/JBTIS-522 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Paul Leacu > Assignee: Paul Leacu > > The IS is now at 9.0.0.GA/ 4.3.0.Final - update the community side. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 10:45:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 10:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119507#comment-13119507 ] Nick Boldt commented on JBTIS-508: ---------------------------------- 9.0/development sites look good after the Alpha2 release. However, we need to look at the publishing of CI (snapshots) so they appears here: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/ https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/earlyaccess/ instead of here: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/discovery/9.0.0.Beta1/earlyaccess/ and the staging URLs are not as current as the /development/ ones, so that should be fixed too. Ideally, /staging/ should be equal to or NEWER than what's in /development/. https://devstudio.redhat.com/9.0/staging/updates/integration-stack/ https://devstudio.redhat.com/9.0/staging/updates/integration-stack/earlyaccess/ > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 12:49:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 12:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-20992: ---------------------------------- Summary: Why is freemarker build failing to deploy to nexus? Key: JBIDE-20992 URL: https://issues.jboss.org/browse/JBIDE-20992 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, freemarker Affects Versions: 4.3.1.Beta1 Reporter: Nick Boldt Priority: Critical Attachments: deployment.fail.txt Freemarker build is failing to deploy the site to nexus. Log snippet: [^deployment.fail.txt] Far as I can tell (?) there's: * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) * no significant difference when comparing root poms [2], [3] [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 -- Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? -- (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 12:54:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20992: ------------------------------- Description: Freemarker build is failing to deploy the site to nexus. Log snippet: [^deployment.fail.txt], taken from * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) vs. * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) Far as I can tell (?) there's: * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) * no significant difference when comparing root poms [2], [3] [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 -- Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? -- (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) was: Freemarker build is failing to deploy the site to nexus. Log snippet: [^deployment.fail.txt] Far as I can tell (?) there's: * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) * no significant difference when comparing root poms [2], [3] [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 -- Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? -- (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Priority: Critical > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 12:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20992: ---------------------------------- Assignee: Mickael Istria > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 12:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20992: ------------------------------- Fix Version/s: 4.3.1.Beta1 > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 13:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 13:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Attachment: JBIDE20976_NeonM2_sapphire.png JBIDE20976_NeonM2.png Looks like the problem is that the bits pulled into Neon M1 were from June/July 2015, and so are older than those in Mars.1. Solution: move target platforms 4.60.0.Alpha1 to use Neon M2, which contains newer or at least equivalent content. !JBIDE20976_NeonM2.png! !JBIDE20976_NeonM2_sapphire.png! > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs: > {code} > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.pde 3.11.1.v20150904-0015 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 13:26:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 13:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Description: Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). Details in these logs: http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html Affected IUs (now sorted alphabetically): {code} org.eclipse.core.runtime 3.11.1.v20150903-1804 org.eclipse.egit 4.0.2.201509141540-r org.eclipse.egit.core 4.0.2.201509141540-r org.eclipse.egit.doc 4.0.2.201509141540-r org.eclipse.egit.ui 4.0.2.201509141540-r org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 org.eclipse.jdt 3.11.1.v20150904-0015 org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 org.eclipse.jetty.webapp 9.2.13.v20150730 org.eclipse.jetty.xml 9.2.13.v20150730 org.eclipse.jgit 4.0.2.201509141540-r org.eclipse.jgit.archive 4.0.2.201509141540-r org.eclipse.jst.common.frameworks 1.1.701.v201509021802 org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 org.eclipse.jst.web_core.feature 3.7.1.v201509021802 org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 org.eclipse.pde 3.11.1.v20150904-0345 org.eclipse.pde.doc.user 3.11.1.v20150903-1352 org.eclipse.platform 4.5.1.v20150904-0015 org.eclipse.platform.doc.user 4.5.1.v20150819-1130 org.eclipse.rcp 4.5.1.v20150904-0015 org.eclipse.sapphire 9.0.1.201509151939 org.eclipse.sapphire.java 9.0.1.201509151939 org.eclipse.sapphire.java.jdt 9.0.1.201509151939 org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 org.eclipse.sapphire.modeling 9.0.1.201509151939 org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 org.eclipse.sapphire.osgi 9.0.1.201509151939 org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 org.eclipse.sapphire.platform 9.0.1.201509151939 org.eclipse.sapphire.ui 9.0.1.201509151939 org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 org.eclipse.sapphire.workspace 9.0.1.201509151939 org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 org.eclipse.swt 3.104.1.v20150825-0743 org.eclipse.wst.common_core.feature 3.7.1.v201508262220 org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 org.eclipse.wst.server.core 1.7.0.v201508271522 org.eclipse.wst.server.discovery 1.1.0.v201508271522 org.eclipse.wst.server.ui 1.5.201.v201509022125 org.eclipse.wst.server_core.feature 3.3.600.v201508271522 org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 org.eclipse.wst.validation 1.2.700.v201508251749 org.eclipse.wst.web_core.feature 3.7.1.v201508271605 org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 {code} was: Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). Details in these logs: http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html Affected IUs: {code} org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 org.eclipse.jst.web_core.feature 3.7.1.v201509021802 org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 org.eclipse.sapphire.java 9.0.1.201509151939 org.eclipse.jgit 4.0.2.201509141540-r org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 org.eclipse.sapphire.platform 9.0.1.201509151939 org.eclipse.rcp 4.5.1.v20150904-0015 org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 org.eclipse.sapphire 9.0.1.201509151939 org.eclipse.wst.server_core.feature 3.3.600.v201508271522 org.eclipse.wst.web_core.feature 3.7.1.v201508271605 org.eclipse.egit 4.0.2.201509141540-r org.eclipse.pde 3.11.1.v20150904-0345 org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 org.eclipse.sapphire.ui 9.0.1.201509151939 org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 org.eclipse.sapphire.java.jdt 9.0.1.201509151939 org.eclipse.wst.common_core.feature 3.7.1.v201508262220 org.eclipse.sapphire.osgi 9.0.1.201509151939 org.eclipse.jdt 3.11.1.v20150904-0015 org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 org.eclipse.egit.core 4.0.2.201509141540-r org.eclipse.wst.server.discovery 1.1.0.v201508271522 org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 org.eclipse.wst.server.core 1.7.0.v201508271522 org.eclipse.platform.doc.user 4.5.1.v20150819-1130 org.eclipse.platform 4.5.1.v20150904-0015 org.eclipse.core.runtime 3.11.1.v20150903-1804 org.eclipse.jetty.webapp 9.2.13.v20150730 org.eclipse.egit.ui 4.0.2.201509141540-r org.eclipse.rcp 4.5.1.v20150904-0015 org.eclipse.jdt 3.11.1.v20150904-0015 org.eclipse.sapphire.java.jdt 9.0.1.201509151939 org.eclipse.pde 3.11.1.v20150904-0015 org.eclipse.swt 3.104.1.v20150825-0743 org.eclipse.jetty.xml 9.2.13.v20150730 org.eclipse.sapphire.ui 9.0.1.201509151939 org.eclipse.egit.doc 4.0.2.201509141540-r org.eclipse.jgit.archive 4.0.2.201509141540-r org.eclipse.jgit 4.0.2.201509141540-r org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 org.eclipse.egit 4.0.2.201509141540-r org.eclipse.sapphire.workspace 9.0.1.201509151939 org.eclipse.wst.server.ui 1.5.201.v201509022125 org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 org.eclipse.sapphire.java 9.0.1.201509151939 org.eclipse.sapphire.modeling 9.0.1.201509151939 org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 org.eclipse.pde.doc.user 3.11.1.v20150903-1352 org.eclipse.wst.validation 1.2.700.v201508251749 org.eclipse.jst.common.frameworks 1.1.701.v201509021802 org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 org.eclipse.sapphire.platform 9.0.1.201509151939 org.eclipse.sapphire.osgi 9.0.1.201509151939 {code} > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 13:38:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 13:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20976: ---------------------------------- Assignee: Nick Boldt (was: Mickael Istria) > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 13:48:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 19 Oct 2015 13:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119585#comment-13119585 ] Nick Boldt commented on JBIDE-20992: ------------------------------------ Related: https://issues.jboss.org/browse/ORG-2485 > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 15:44:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 15:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119621#comment-13119621 ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- feedback on installer: shouldn't the feature selection be before the runtime selection? > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 15:48:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 15:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119622#comment-13119622 ] Paul Leacu commented on JBDS-3276: ---------------------------------- Hey [~maxandersen] - This comes as a request from [~crobson] [~john.graham] and Ken Johnson to construct a simplified installation mechanism for a specific tool product set. They asked for Fuse Tooling. Basically they were looking for a prototype-demonstration only installer to do an A/B test. I agree that this Jira is for discussion surrounding a standalone JBDSIS installer. I'll create a new one and link to you, Catherine, John (and anyone else who might be interested). > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 15:53:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 15:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-517. ------------------------------ Fix Version/s: 9.0.0.Alpha2 Resolution: Done web pages updated > Update web pages for JBDS-IS 9.x > -------------------------------- > > Key: JBTIS-517 > URL: https://issues.jboss.org/browse/JBTIS-517 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.Alpha2 > > Attachments: jbdsis-900alpha2-webpage.png, jbdsis-900alpha2ea-webpage.png > > > Update web pages for JBDS-IS 9.x at > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ > See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 15:54:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 15:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119625#comment-13119625 ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- and about Fuse perspective: a) it is called Fuse Integration - why not just Fuse ? b) it has no editor area by default so JBoss Central is gone but so are users other editors until you manually open a file. I would say thats not very intuitive. > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:03:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 19 Oct 2015 16:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20907) Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio resolved JBIDE-20907. ---------------------------------- Fix Version/s: 4.3.0.Final Resolution: Done > Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20907 > URL: https://issues.jboss.org/browse/JBIDE-20907 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Minor > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:04:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 19 Oct 2015 16:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20907) Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio closed JBIDE-20907. -------------------------------- Re-opened to set FixVersion. > Correct timeouts seen with: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20907 > URL: https://issues.jboss.org/browse/JBIDE-20907 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Minor > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:13:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 19 Oct 2015 16:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio updated JBDS-3276: ------------------------------- Attachment: JBDSIS_installer_space.png JBDSIS_installer_9.png > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:13:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 19 Oct 2015 16:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119630#comment-13119630 ] Len DiMaggio commented on JBDS-3276: ------------------------------------ Found a couple of other issues: !JBDSIS_installer_9.png|thumbnail! !JBDSIS_installer_space.png|thumbnail! > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:15:01 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 16:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: Paul Leacu created JBTIS-523: -------------------------------- Summary: Create a demonstration/ prototype installer for Fuse Tooling support Key: JBTIS-523 URL: https://issues.jboss.org/browse/JBTIS-523 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: distribution Affects Versions: 9.0.0.GA Reporter: Paul Leacu Assignee: Paul Leacu Priority: Optional The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. JBDS comes up in the Fuse Integration perspective - read to go. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:16:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 16:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-523: ----------------------------- Description: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. JBDS comes up in the Fuse Integration perspective - read to go. {code} was: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. JBDS comes up in the Fuse Integration perspective - read to go. {code} > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. JBDS comes up in the Fuse Integration perspective - read to go. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:16:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 16:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-523: ----------------------------- Attachment: sai1.png > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. JBDS comes up in the Fuse Integration perspective - read to go. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:17:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 16:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-523: ----------------------------- Description: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart JBDS comes up in the Fuse Integration perspective - read to go. {code} was: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. JBDS comes up in the Fuse Integration perspective - read to go. {code} > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:20:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 19 Oct 2015 16:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-523: ----------------------------- Description: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart JBDS comes up in the Fuse Integration perspective - read to go. {code} Comments welcome! was: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. An future option here would be to create an installer with *just* the Fuse Tooling components available. ANother future option would be to change the default perspective to the component-specific perspective (i.e. Fise Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart JBDS comes up in the Fuse Integration perspective - read to go. {code} > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} > Comments welcome! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:34:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 16:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119639#comment-13119639 ] Max Rydahl Andersen commented on JBIDE-20991: --------------------------------------------- suggestion on one approach, add a runtime detector that will recognize: /VagrantFile /.cdk <- file with content we can use to name the server, identify the ip it is running etc. (if there are no good defaults) > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:38:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 16:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119639#comment-13119639 ] Max Rydahl Andersen edited comment on JBIDE-20991 at 10/19/15 4:37 PM: ----------------------------------------------------------------------- suggestion on one approach, add a runtime detector that will recognize: /VagrantFile /.cdk <- file with content we can use to name the server, identify the ip it is running etc. (if there are no good defaults) pseudocode suggestion: {code} docker.url=https://172.1.2.3:3434 openshift.url=https://..... cdk.ip=172.1.4.3 {code} was (Author: maxandersen): suggestion on one approach, add a runtime detector that will recognize: /VagrantFile /.cdk <- file with content we can use to name the server, identify the ip it is running etc. (if there are no good defaults) > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:39:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 16:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119641#comment-13119641 ] Max Rydahl Andersen commented on JBIDE-20991: --------------------------------------------- maybe it will be enough to call vagrant adbinfo to get all this. Talk to [~xcoulon] what will be there. > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:45:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 16:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-20993: ------------------------------------------- Summary: http://download.jboss.org/jbosstools/ contains wrong versions Key: JBIDE-20993 URL: https://issues.jboss.org/browse/JBIDE-20993 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Max Rydahl Andersen while discussing download.jboss.org with [~dgolovin] we found http://download.jboss.org/jbosstools/9.0/ http://download.jboss.org/jbosstools/10.0/ These look to be links to mars and neon. This is mixing in devstudio versioning with jbosstools which is just really confusing. No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:57:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 19 Oct 2015 16:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio updated JBDS-3276: ------------------------------- Attachment: EA.png > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:57:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 19 Oct 2015 16:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119630#comment-13119630 ] Len DiMaggio edited comment on JBDS-3276 at 10/19/15 4:56 PM: -------------------------------------------------------------- Found a couple of other issues: !JBDSIS_installer_9.png|thumbnail! !JBDSIS_installer_space.png|thumbnail! !EA.png|thumbnail! was (Author: ldimaggio): Found a couple of other issues: !JBDSIS_installer_9.png|thumbnail! !JBDSIS_installer_space.png|thumbnail! > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 16:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 16:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20989) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119648#comment-13119648 ] Alexey Kazakov commented on JBIDE-20989: ---------------------------------------- Please create a PR for 4.3.x too. We can't cherry pick it from master because the plugin was renamed. > Preference validation fails on windows if node executable called node64.exe > --------------------------------------------------------------------------- > > Key: JBIDE-20989 > URL: https://issues.jboss.org/browse/JBIDE-20989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Beta1 > > > For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). > Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:06:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 17:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119649#comment-13119649 ] Max Rydahl Andersen commented on JBTIS-508: ------------------------------------------- should updates/integration-stack/ and updates/integration-stack not just be a composites that points to the relevant version specific content ? i.e. seems wrong to me to suggest it is "instead", its just about using the right composites, right? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:16:02 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:16:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20969) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20969: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files > ------------------------------------------------------------------------------------- > > Key: JBIDE-20969 > URL: https://issues.jboss.org/browse/JBIDE-20969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Daniel Azarov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: broken-hyperlink.xml > > > If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log > {noformat} > ava.lang.NullPointerException > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) > at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20969) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20969: ----------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files > ------------------------------------------------------------------------------------- > > Key: JBIDE-20969 > URL: https://issues.jboss.org/browse/JBIDE-20969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Daniel Azarov > Fix For: 4.3.1.Beta1 > > Attachments: broken-hyperlink.xml > > > If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log > {noformat} > ava.lang.NullPointerException > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) > at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20994) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20994: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files > ------------------------------------------------------------------------------------- > > Key: JBIDE-20994 > URL: https://issues.jboss.org/browse/JBIDE-20994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Daniel Azarov > Fix For: 4.4.0.Alpha1 > > Attachments: broken-hyperlink.xml > > > If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log > {noformat} > ava.lang.NullPointerException > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) > at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20994) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-20994: -------------------------------------- Summary: NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files Key: JBIDE-20994 URL: https://issues.jboss.org/browse/JBIDE-20994 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.3.0.Final Reporter: Fred Bricon Assignee: Daniel Azarov Fix For: 4.3.1.Beta1 If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log {noformat} ava.lang.NullPointerException at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) 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:1499) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) 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) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20994) NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20994. ------------------------------------ Resolution: Done > NPE in BatchHyperlinkDetector.getBatchProject when Ctrl+Hover links in external files > ------------------------------------------------------------------------------------- > > Key: JBIDE-20994 > URL: https://issues.jboss.org/browse/JBIDE-20994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Daniel Azarov > Fix For: 4.4.0.Alpha1 > > Attachments: broken-hyperlink.xml > > > If you open an external file via the File > Open File... menu, then Ctrl+Hover links in that file, BatchHyperlinkDetector.getBatchProject throws an NPE, shown in Eclipse's log > {noformat} > ava.lang.NullPointerException > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.getBatchProject(BatchHyperlinkDetector.java:140) > at org.jboss.tools.batch.ui.hyperlink.BatchHyperlinkDetector.detectHyperlinks(BatchHyperlinkDetector.java:43) > at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261) > at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:25:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 17:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119651#comment-13119651 ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- [~pleacu] okey sounds great - and yes, I think if that is the goal (to have a good out of box experience for a more narrow toolset) then that requires more work than just "set first perspective to Fuse". but lets handle that on separate jira issue. > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:29:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 19 Oct 2015 17:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119652#comment-13119652 ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- [~ldimaggio] you two first screenshots are bugs, the last one with earlyaccess installed is 100% correct and shows that the system is working. The installer currently bundles *everything* meaning also earlyaccess content and thus it will when installed be detected as earlyaccess and you get this warning. This is no different if you enabled earlyaccess, installed something and then disabled earlyaccess. You would still have earlyaccess content installed and we would let you know. So there are two solutions to this : a) either we add earlyaccess support to the installer to differentiate or b) don't have earlyaccess content in the final installer (meaning if we built the installer today for release it would only contain the old SOA tooling) B is what we had discussed in the past. > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:31:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBDS-3093. -------------------------------- Fix Version/s: 9.1.0.Beta1 (was: LATER) Resolution: Rejected OK. Closing the issue then. > Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access? > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3093 > URL: https://issues.jboss.org/browse/JBDS-3093 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: central, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.Beta1 > > > Max said: > {quote} > This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. > Thus lets discuss how far we are ok (in principle/not technical terms) early access goes > A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? > I assume YES because that is what the early access feature does that everyone was fine with before. > B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) > I assume YES since this has zero technical difference from A > C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? > I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see > But if you cannot even agree to it by principle then any technical discussion is pointless. > Thus can you give Yes/No answers to the above please ? > My answers are: > A) Yes > B) Yes > C) Yes > ...all with the assumption we make it clear that once you do this you are running in "early access" mode. > For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:44:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20993: -------------------------------------- Assignee: Nick Boldt > http://download.jboss.org/jbosstools/ contains wrong versions > ------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:44:01 2015 From: issues at jboss.org (Jiri Pallich (JIRA)) Date: Mon, 19 Oct 2015 17:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119659#comment-13119659 ] Jiri Pallich commented on JBIDE-20609: -------------------------------------- +1 from PgM > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 17:44:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 19 Oct 2015 17:44:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20993: ----------------------------------- Fix Version/s: 4.3.1.Beta1 > http://download.jboss.org/jbosstools/ contains wrong versions > ------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 18:23:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 19 Oct 2015 18:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20990: ---------------------------------- Involved: Denis Golovin > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 18:24:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 19 Oct 2015 18:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Golovin updated JBIDE-20991: ---------------------------------- Involved: Denis Golovin > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 18:34:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Mon, 19 Oct 2015 18:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119662#comment-13119662 ] Denis Golovin commented on JBIDE-20991: --------------------------------------- Would be bellow URL's good default values? {code}https://${cdk.ip}:2375 for docker https://${cdk.ip}:8443 for openshift{code} [~xcoulon], [~adietish] WDYT? > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 04:24:00 2015 From: issues at jboss.org (David Hladky (JIRA)) Date: Tue, 20 Oct 2015 04:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: David Hladky created JBDS-3547: ---------------------------------- Summary: Eloqua tracking of Eloqua tracked links Key: JBDS-3547 URL: https://issues.jboss.org/browse/JBDS-3547 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: website Affects Versions: 9.0.0.GA Reporter: David Hladky I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 05:19:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Tue, 20 Oct 2015 05:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20995) CDK runs Docker 1.7.1 which fails on returning search results In-Reply-To: References: Message-ID: Xavier Coulon created JBIDE-20995: ------------------------------------- Summary: CDK runs Docker 1.7.1 which fails on returning search results Key: JBIDE-20995 URL: https://issues.jboss.org/browse/JBIDE-20995 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Reporter: Xavier Coulon When searching for an image on DockerHub via a connection to CDK, Eclipse reports this kind of error: {code} Caused by: org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/plain; charset=utf-8, type=interface java.util.List, genericType=java.util.List. at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:230) at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:154) at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1124) {code} which is caused by this bug in Docker: https://github.com/docker/docker/pull/14850 This bug has been fixed in Docker 1.8: https://github.com/docker/docker/commit/5328cc346f56beae2f5a230d445ebdc5b784e6c1 so the Docker version in CDK needs to be upgraded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 05:21:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Tue, 20 Oct 2015 05:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3548) CDK runs Docker 1.7.1 which fails on returning search results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon updated JBDS-3548: -------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: Tools (JBoss Tools)) Key: JBDS-3548 (was: JBIDE-20995) Workflow: CDW v1 (was: GIT Pull Request workflow ) Docs QE Status: NEW Component/s: docker (was: docker) Affects Testing: Blocks Testing > CDK runs Docker 1.7.1 which fails on returning search results > ------------------------------------------------------------- > > Key: JBDS-3548 > URL: https://issues.jboss.org/browse/JBDS-3548 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: docker > Affects Versions: 9.0.0.GA > Reporter: Xavier Coulon > > When searching for an image on DockerHub via a connection to CDK, Eclipse reports this kind of error: > {code} > Caused by: org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/plain; charset=utf-8, type=interface java.util.List, genericType=java.util.List. > at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:230) > at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:154) > at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1124) > {code} > which is caused by this bug in Docker: https://github.com/docker/docker/pull/14850 > This bug has been fixed in Docker 1.8: https://github.com/docker/docker/commit/5328cc346f56beae2f5a230d445ebdc5b784e6c1 so the Docker version in CDK needs to be upgraded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 05:21:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Tue, 20 Oct 2015 05:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3548) CDK runs Docker 1.7.1 which fails on returning search results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon updated JBDS-3548: -------------------------------- Priority: Blocker (was: Major) > CDK runs Docker 1.7.1 which fails on returning search results > ------------------------------------------------------------- > > Key: JBDS-3548 > URL: https://issues.jboss.org/browse/JBDS-3548 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: docker > Affects Versions: 9.0.0.GA > Reporter: Xavier Coulon > Priority: Blocker > > When searching for an image on DockerHub via a connection to CDK, Eclipse reports this kind of error: > {code} > Caused by: org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/plain; charset=utf-8, type=interface java.util.List, genericType=java.util.List. > at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:230) > at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:154) > at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1124) > {code} > which is caused by this bug in Docker: https://github.com/docker/docker/pull/14850 > This bug has been fixed in Docker 1.8: https://github.com/docker/docker/commit/5328cc346f56beae2f5a230d445ebdc5b784e6c1 so the Docker version in CDK needs to be upgraded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 05:21:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Tue, 20 Oct 2015 05:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3548) CDK runs Docker 1.7.1 which fails on returning search results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon updated JBDS-3548: -------------------------------- Affects Version/s: 9.0.0.GA > CDK runs Docker 1.7.1 which fails on returning search results > ------------------------------------------------------------- > > Key: JBDS-3548 > URL: https://issues.jboss.org/browse/JBDS-3548 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: docker > Affects Versions: 9.0.0.GA > Reporter: Xavier Coulon > Priority: Blocker > > When searching for an image on DockerHub via a connection to CDK, Eclipse reports this kind of error: > {code} > Caused by: org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/plain; charset=utf-8, type=interface java.util.List, genericType=java.util.List. > at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:230) > at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:154) > at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1124) > {code} > which is caused by this bug in Docker: https://github.com/docker/docker/pull/14850 > This bug has been fixed in Docker 1.8: https://github.com/docker/docker/commit/5328cc346f56beae2f5a230d445ebdc5b784e6c1 so the Docker version in CDK needs to be upgraded. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 06:10:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Tue, 20 Oct 2015 06:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20988) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Buziuk updated JBIDE-20988: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/540, https://github.com/jbosstools/jbosstools-jst/pull/541 (was: https://github.com/jbosstools/jbosstools-jst/pull/540) > Preference validation fails on windows if node executable called node64.exe > --------------------------------------------------------------------------- > > Key: JBIDE-20988 > URL: https://issues.jboss.org/browse/JBIDE-20988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). > Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 06:10:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Tue, 20 Oct 2015 06:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20988) Preference validation fails on windows if node executable called node64.exe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119784#comment-13119784 ] Ilya Buziuk commented on JBIDE-20988: ------------------------------------- PR with test - https://github.com/jbosstools/jbosstools-jst/pull/541 > Preference validation fails on windows if node executable called node64.exe > --------------------------------------------------------------------------- > > Key: JBIDE-20988 > URL: https://issues.jboss.org/browse/JBIDE-20988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > For windows node executable can be named either *node.exe* or *node64.exe* (compiled against the 64 bit version of V8). > Node preference validation fails for 64-bit version. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 06:23:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Tue, 20 Oct 2015 06:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Hopp closed JBIDE-19944. ------------------------------ Verified in JBDS 8.1 and 9.0. Closing. > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Final > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-product > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 06:26:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Tue, 20 Oct 2015 06:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20917) Wrong default name for java ee 7 archetypes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Hopp closed JBIDE-20917. ------------------------------ Verified in JBDS 9.0.0. Closing. > Wrong default name for java ee 7 archetypes > ------------------------------------------- > > Key: JBIDE-20917 > URL: https://issues.jboss.org/browse/JBIDE-20917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.0.Final > > > It looks like if the archetype does not provide default name, package etc. Some default values are used (for EAR project it is "jboss-javaee6-multi"). This name is not right at least in situation, when JavaEE7 archetype is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:03:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Tue, 20 Oct 2015 07:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? In-Reply-To: References: Message-ID: Radim Hopp created JBIDE-20996: ---------------------------------- Summary: DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? Key: JBIDE-20996 URL: https://issues.jboss.org/browse/JBIDE-20996 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: runtime-detection Affects Versions: 4.3.0.Final Reporter: Radim Hopp It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. Is there anything we could do to make this workflow easier. Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:04:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Tue, 20 Oct 2015 07:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20769) Add JBoss DV 6.2 to Download Runtimes Wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Hopp closed JBIDE-20769. ------------------------------ Verified in JBDS 9.0.0. I've created followup jira: JBIDE-20996 > Add JBoss DV 6.2 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-20769 > URL: https://issues.jboss.org/browse/JBIDE-20769 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > JBoss DV 6.2 was released 5 days ago. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-852. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:05:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Tue, 20 Oct 2015 07:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Hopp closed JBIDE-19852. ------------------------------ Verified in JBDS 9.0.0. The installation path is predefined. But in case of DV 6.2 it's a bit misleading as it demands path to existing EAP 6.4 -> I've created a followup jira JBIDE-20996 > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home//downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home//downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home//DV) > 5. Finish installer > ASSERT: /home//DV is added to runtime-detection paths instead of /home//downloadedDV -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:07:00 2015 From: issues at jboss.org (Radim Hopp (JIRA)) Date: Tue, 20 Oct 2015 07:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20710) tools.jboss.org/features: Update Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Hopp closed JBIDE-20710. ------------------------------ Verified. Closing. > tools.jboss.org/features: Update Central > ---------------------------------------- > > Key: JBIDE-20710 > URL: https://issues.jboss.org/browse/JBIDE-20710 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Fix For: 4.3.0.Final > > > We should update http://tools.jboss.org/features/central.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:43:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Tue, 20 Oct 2015 07:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20997) Should not be able to create duplicative labels In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-20997: ------------------------------------- Summary: Should not be able to create duplicative labels Key: JBIDE-20997 URL: https://issues.jboss.org/browse/JBIDE-20997 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Final Reporter: Mari?n Labuda User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name. But as a result only the last one is created (it looks like others are either ignored or overwrite). It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:45:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Tue, 20 Oct 2015 07:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20998) Validation error description in Resource Labels dialog is cut off In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-20998: ------------------------------------- Summary: Validation error description in Resource Labels dialog is cut off Key: JBIDE-20998 URL: https://issues.jboss.org/browse/JBIDE-20998 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Final Reporter: Mari?n Labuda Attachments: resource_label_complete.png, resource_label_incomplete.png In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description: !resource_label_incomplete.png! And following image contains full description after resizing to "long enough" width: !resource_label_complete.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:52:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Tue, 20 Oct 2015 07:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20999) Validation error for a new label is not accurate In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-20999: ------------------------------------- Summary: Validation error for a new label is not accurate Key: JBIDE-20999 URL: https://issues.jboss.org/browse/JBIDE-20999 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Final Reporter: Mari?n Labuda In Resource Label dialog opened from New OpenShift Application wizard there is a validation error description informing users about correct form of a new label. This description is not accurate. First inaccurate description is the one with empty label name/value (if one of them is empty). There is missing information about possible characters (underscore, slash). Label value validation error description does not contain information about underscore. Also there should be mentioned that also upper case letters are allowed - in validation error description are mentioned only lower case letters. For more reference about proper format of a label see kubernetes doc at http://kubernetes.io/v1.0/docs/user-guide/labels.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 07:55:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Tue, 20 Oct 2015 07:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21000) "Remove" button in New OpenShift Application wizard page should be "Remove..." In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-21000: ------------------------------------- Summary: "Remove" button in New OpenShift Application wizard page should be "Remove..." Key: JBIDE-21000 URL: https://issues.jboss.org/browse/JBIDE-21000 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Final Reporter: Mari?n Labuda Remove button located on the 3rd New OpenShift Application wizard page (the one with resource labels) should have label "Remove..." instead of "Removed". It's because there is invoked dialog for removal confirmation of a label. If it would be Remove, then no confirmation would be expected. We use this approach all over the wizards and dialogs - if there is expected further user interaction, the "..." should follow a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 08:37:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Tue, 20 Oct 2015 08:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20984) Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119893#comment-13119893 ] Snjezana Peco commented on JBIDE-20984: --------------------------------------- I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=480206. > Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20984 > URL: https://issues.jboss.org/browse/JBIDE-20984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, upstream > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBoss - JBoss Central - JBoss Developer Studio _001.png > > > Default JBDS installation contains "Arquillia Cruiser" (missing n) view. Arquillian from central isn't installed. View is missing icon and does not work at all - if you try to open it you will get view with "Could not create the view: org.jboss.tools.arquillian.ui.views.arquillianView" text. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 08:40:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Tue, 20 Oct 2015 08:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20984) Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20984: ---------------------------------- Component/s: (was: arquillian) > Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20984 > URL: https://issues.jboss.org/browse/JBIDE-20984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBoss - JBoss Central - JBoss Developer Studio _001.png > > > Default JBDS installation contains "Arquillia Cruiser" (missing n) view. Arquillian from central isn't installed. View is missing icon and does not work at all - if you try to open it you will get view with "Could not create the view: org.jboss.tools.arquillian.ui.views.arquillianView" text. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 08:52:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 20 Oct 2015 08:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119920#comment-13119920 ] Paul Leacu commented on JBDS-3276: ---------------------------------- FYI - for the simplified Fuse Tooling installation discussion see https://issues.jboss.org/browse/JBTIS-523 > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:16:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 09:16:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119507#comment-13119507 ] Nick Boldt edited comment on JBTIS-508 at 10/20/15 9:15 AM: ------------------------------------------------------------ 9.0/development sites look good after the Alpha2 release: * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ However, we need to look at the publishing of CI (snapshots) so they appears here: * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/ * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/earlyaccess/ instead of here: * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/discovery/9.0.0.Beta1/earlyaccess/ and the staging URLs are not as current as the /development/ ones, so that should be fixed too. Ideally, /staging/ should be equal to or NEWER than what's in /development/. * https://devstudio.redhat.com/9.0/staging/updates/integration-stack/ * https://devstudio.redhat.com/9.0/staging/updates/integration-stack/earlyaccess/ was (Author: nickboldt): 9.0/development sites look good after the Alpha2 release. However, we need to look at the publishing of CI (snapshots) so they appears here: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/ https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/earlyaccess/ instead of here: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/discovery/9.0.0.Beta1/earlyaccess/ and the staging URLs are not as current as the /development/ ones, so that should be fixed too. Ideally, /staging/ should be equal to or NEWER than what's in /development/. https://devstudio.redhat.com/9.0/staging/updates/integration-stack/ https://devstudio.redhat.com/9.0/staging/updates/integration-stack/earlyaccess/ > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:20:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 09:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119952#comment-13119952 ] Nick Boldt commented on JBTIS-508: ---------------------------------- Yes, the links to which I refer are *composites*, with actual version numbers carefully hidden underneath. Like we do for JBT and JBDS. My point when saying "instead" is that the pattern of * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/ * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/earlyaccess/ more closely aligns with the pattern of * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ thus making release process easier.... rather than linking to something like https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/discovery/9.0.0.Beta1/earlyaccess/ which would then include many nearly-duplicate early access plugin jars (see problems with this reported in JBTIS-498), and have a version-specific path segment. As I've said before only staging sites ought to have a version-specific URL because that way QE can differentiate between CR1 and CR1a. For CI builds, we only need a latest build and for development & stable, we definitely only want the latest. Make sense? It's the same protocol we're using for JBT & JBDS, so I hope you're OK with this, Max. :D > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:21:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 20 Oct 2015 09:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119954#comment-13119954 ] Max Rydahl Andersen commented on JBDS-3547: ------------------------------------------- can you be a bit more specific please ? The urls we have are the ones given to us. Do you mean that urls as listed at https://github.com/jbosstools/jbosstools-website/blob/master/_config/products.yml#L88 should be http://www.jboss.org/download-manager/content/origin/files/sha256/b5/b55d3b959d4922f69338095aff4d3cea639766a7c07850e539ebc0b9029e8902/jboss-devstudio-9.0.0.GA-installer-standalone.jar instead of http://www.redhat.com/j/elqNow/elqRedir.htm?ref=http://www.jboss.org/download-manager/content/origin/files/sha256/b5/b55d3b959d4922f69338095aff4d3cea639766a7c07850e539ebc0b9029e8902/jboss-devstudio-9.0.0.GA-installer-standalone.jar ? How about the other eloqua tracking on the site ? btw. it was all reviewed and approved earlier so I assume this is a recent change ? > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:27:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 20 Oct 2015 09:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119963#comment-13119963 ] Paul Leacu commented on JBTIS-508: ---------------------------------- Will do. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:38:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118424#comment-13118424 ] Jeff Cantrill edited comment on JBIDE-20601 at 10/20/15 9:37 AM: ----------------------------------------------------------------- [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based clarification pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports was (Author: jcantrill): [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service Current implementation produces the former which is what we desire. What more do we need to provide? It seems to me we should allow a user to modify the exposed port which should be addressed in JBIDE-20531. We may need additional prompts and texts to clarify what this page allows you to configure. User's may wish to have additional routes, but I think that should be a follow-on action; this flow is supposed to be the fastest path to deploying an image. We should consider closing this issue or modifying it to reflect the need for additional verbiage for the user. > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:38:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118424#comment-13118424 ] Jeff Cantrill edited comment on JBIDE-20601 at 10/20/15 9:37 AM: ----------------------------------------------------------------- [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based clarification {{pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports }} was (Author: jcantrill): [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based clarification pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:39:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 09:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118424#comment-13118424 ] Jeff Cantrill edited comment on JBIDE-20601 at 10/20/15 9:38 AM: ----------------------------------------------------------------- [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based clarification: pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports was (Author: jcantrill): [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based clarification {{pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports }} > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:39:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 09:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118424#comment-13118424 ] Jeff Cantrill edited comment on JBIDE-20601 at 10/20/15 9:38 AM: ----------------------------------------------------------------- [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based on getting clarification: pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports was (Author: jcantrill): [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based clarification: pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:45:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Tue, 20 Oct 2015 09:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119983#comment-13119983 ] Supriya Bharadwaj commented on TOOLSDOC-307: -------------------------------------------- > Completed the document at: https://docs.google.com/document/d/19J_RDjHIIo_gtZrPKw87Kqgld3bMfFjHpVDpcrrAJIk/edit > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 10:28:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 10:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119674#comment-13119674 ] Nick Boldt edited comment on JBIDE-20976 at 10/20/15 10:27 AM: --------------------------------------------------------------- PR to: * pull in newer WTP, Jetty, and Neon M2 bundles * add org.eclipse.core.runtime.compatibility since org.eclipse.datatools requires it * pull egit/v4.1.0.201509280440-r instead of 4.0.0 to get newer org.eclipse.egit.ui.importer https://github.com/jbosstools/jbosstools-target-platforms/pull/169 was (Author: nickboldt): PR to pull in newer WYP, Jetty, and Neon M2 bundles: https://github.com/jbosstools/jbosstools-target-platforms/pull/169 > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 10:37:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 10:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Attachment: p2diff-all.txt p2diff-summary.txt {code} p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO/ file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ | egrep -v "source|sdk|doc.isv" | tee p2diff-all.txt {code} --> [^p2diff-all.txt] (Note that the unique IU count is too high for the local build because I included source/doc bundles when resolving the TP; that's why I removed them via grep from the log.) {code}p2diff-check.sh p2diff-all.txt | tee p2diff-summary.txt -org.eclipse.jetty.xml -org.eclipse.jetty.webapp -org.eclipse.egit.ui.importer +org.eclipse.core.runtime.compatibility.registry +com.jcraft.jsch > org.eclipse.jetty.xml [9.3.2.v20150730] > org.eclipse.jetty.webapp [9.3.2.v20150730] > org.eclipse.egit.ui.importer [4.1.0.201509280440-r] < org.eclipse.core.runtime.compatibility.registry [3.6.0.v20150318-1505] < com.jcraft.jsch [0.1.51.v201410302000] {code} Note: p2diff-check.sh is https://gist.github.com/nickboldt/0c240b272cfb54d40374/ > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 10:37:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 10:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120032#comment-13120032 ] Nick Boldt edited comment on JBIDE-20976 at 10/20/15 10:36 AM: --------------------------------------------------------------- {code} p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO/ file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ | egrep -v "source|sdk|doc.isv" | tee p2diff-all.txt {code} --> [^p2diff-all.txt] (Note that the unique IU count is too high for the local build because I included source/doc bundles when resolving the TP; that's why I removed them via grep from the log.) {code}p2diff-check.sh p2diff-all.txt | tee p2diff-summary.txt -org.eclipse.jetty.xml -org.eclipse.jetty.webapp -org.eclipse.egit.ui.importer +org.eclipse.core.runtime.compatibility.registry +com.jcraft.jsch > org.eclipse.jetty.xml [9.3.2.v20150730] > org.eclipse.jetty.webapp [9.3.2.v20150730] > org.eclipse.egit.ui.importer [4.1.0.201509280440-r] < org.eclipse.core.runtime.compatibility.registry [3.6.0.v20150318-1505] < com.jcraft.jsch [0.1.51.v201410302000] {code} --> [^p2diff-summary.txt] Note: p2diff-check.sh is https://gist.github.com/nickboldt/0c240b272cfb54d40374/ was (Author: nickboldt): {code} p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO/ file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ | egrep -v "source|sdk|doc.isv" | tee p2diff-all.txt {code} --> [^p2diff-all.txt] (Note that the unique IU count is too high for the local build because I included source/doc bundles when resolving the TP; that's why I removed them via grep from the log.) {code}p2diff-check.sh p2diff-all.txt | tee p2diff-summary.txt -org.eclipse.jetty.xml -org.eclipse.jetty.webapp -org.eclipse.egit.ui.importer +org.eclipse.core.runtime.compatibility.registry +com.jcraft.jsch > org.eclipse.jetty.xml [9.3.2.v20150730] > org.eclipse.jetty.webapp [9.3.2.v20150730] > org.eclipse.egit.ui.importer [4.1.0.201509280440-r] < org.eclipse.core.runtime.compatibility.registry [3.6.0.v20150318-1505] < com.jcraft.jsch [0.1.51.v201410302000] {code} Note: p2diff-check.sh is https://gist.github.com/nickboldt/0c240b272cfb54d40374/ > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 10:45:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 10:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120032#comment-13120032 ] Nick Boldt edited comment on JBIDE-20976 at 10/20/15 10:44 AM: --------------------------------------------------------------- {code} p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO/ file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ | egrep -v "source|sdk|doc.isv" | tee p2diff-all.txt {code} --> [^p2diff-all.txt] (Note that the unique IU count is too high for the local build because I included source/doc bundles when resolving the TP; that's why I removed them via grep from the log.) {code}p2diff-check.sh p2diff-all.txt | tee p2diff-summary.txt > org.eclipse.jetty.xml [9.3.2.v20150730] > org.eclipse.jetty.webapp [9.3.2.v20150730] > org.eclipse.egit.ui.importer [4.1.0.201509280440-r] < org.eclipse.core.runtime.compatibility.registry [3.6.0.v20150318-1505] < com.jcraft.jsch [0.1.51.v201410302000] {code} --> [^p2diff-summary.txt] Note: p2diff-check.sh is https://gist.github.com/nickboldt/0c240b272cfb54d40374/ So, to translate the above: * org.eclipse.core.runtime.compatibility.registry [3.6.0.v20150318-1505] is no longer in the proposed TP, as it's not in Neon M2. * com.jcraft.jsch [0.1.51.v201410302000] has been removed, keeping ONLY 0.1.53.v201508180515 (we currently have both versions) * org.eclipse.jetty.xml [9.3.2.v20150730] replaces 9.2.9.v20150224 * org.eclipse.jetty.webapp [9.3.2.v20150730] replaces 9.2.9.v20150224 * org.eclipse.egit.ui.importer [4.1.0.201509280440-r] replaces 4.0.0.201506090130-r was (Author: nickboldt): {code} p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO/ file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ | egrep -v "source|sdk|doc.isv" | tee p2diff-all.txt {code} --> [^p2diff-all.txt] (Note that the unique IU count is too high for the local build because I included source/doc bundles when resolving the TP; that's why I removed them via grep from the log.) {code}p2diff-check.sh p2diff-all.txt | tee p2diff-summary.txt -org.eclipse.jetty.xml -org.eclipse.jetty.webapp -org.eclipse.egit.ui.importer +org.eclipse.core.runtime.compatibility.registry +com.jcraft.jsch > org.eclipse.jetty.xml [9.3.2.v20150730] > org.eclipse.jetty.webapp [9.3.2.v20150730] > org.eclipse.egit.ui.importer [4.1.0.201509280440-r] < org.eclipse.core.runtime.compatibility.registry [3.6.0.v20150318-1505] < com.jcraft.jsch [0.1.51.v201410302000] {code} --> [^p2diff-summary.txt] Note: p2diff-check.sh is https://gist.github.com/nickboldt/0c240b272cfb54d40374/ > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 10:59:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 10:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Attachment: p2diff.ea.txt p2diff.central.txt p2diff.central.summary.txt p2diff.ea.summary.txt > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 10:59:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 10:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120054#comment-13120054 ] Nick Boldt edited comment on JBIDE-20976 at 10/20/15 10:58 AM: --------------------------------------------------------------- Second PR to update to Mars M2 and AngularJS 1.0.0.201508312121 in Central/Earlyaccess sites: https://github.com/jbosstools/jbosstools-discovery/pull/315 p2diffs show no changes other than simple upversioning of existing IUs. [^p2diff.central.txt] [^p2diff.central.summary.txt] [^p2diff.ea.txt] [^p2diff.ea.summary.txt] was (Author: nickboldt): Second PR to update to Mars M2 and AngularJS 1.0.0.201508312121 in Central/Earlyaccess sites: https://github.com/jbosstools/jbosstools-discovery/pull/315 p2diffs show no changes other than upversioning. > Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9 > ---------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:01:02 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 20 Oct 2015 11:01:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120055#comment-13120055 ] Max Rydahl Andersen commented on JBTIS-508: ------------------------------------------- [~nickboldt] no problems with telling users to use the correct site that will actually receive updates (i.e. https://devstudio.redhat.com/9.0/development/updates/integration-stack/) as opposed to the version specific one. I'm just saying that the version specific site does not go away, it is still here for QE to test against. JBDS IS/JBT IS has this extra challenge that they need the version separated site since they are targeting JBDS 9.0 where as our development might contain JBDS 9.1 bits - thus we are risking a rather gnarly overlap/mismatch of sites in the current model ;/ > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 11:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-21001: ---------------------------------- Summary: Version of AngularJS in Central is older than version used in jbosstools-jst Key: JBIDE-21001 URL: https://issues.jboss.org/browse/JBIDE-21001 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, jsp/jsf/xml/html-source-editing Affects Versions: 4.3.0.Final Reporter: Nick Boldt Version of AngularJS used to build jbosstools-jst [1]: * 1.0.0.201508312121 [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2]: * 0.10.0.201506182210 [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 So, we should put the newer AngularJS in the EA site. But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: {code} org.eclipse.angularjs.ui_1.0.0.201508312121.jar org.eclipse.angularjs.core_1.0.0.201508312121.jar angularjs-eclipse-feature_1.0.0.201508312121.jar {code} So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 11:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21001: ---------------------------------- Assignee: Alexey Kazakov > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2]: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 11:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21001: ------------------------------- Fix Version/s: 4.3.1.Beta1 > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2]: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:26:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 11:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21001: ------------------------------- Fix Version/s: 4.4.0.Alpha1 > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2]: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:26:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 11:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21001: ------------------------------- Description: Version of AngularJS used to build jbosstools-jst [1]: * 1.0.0.201508312121 [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: * 0.10.0.201506182210 [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 So, we should put the newer AngularJS in the EA site. But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: {code} org.eclipse.angularjs.ui_1.0.0.201508312121.jar org.eclipse.angularjs.core_1.0.0.201508312121.jar angularjs-eclipse-feature_1.0.0.201508312121.jar {code} So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ was: Version of AngularJS used to build jbosstools-jst [1]: * 1.0.0.201508312121 [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2]: * 0.10.0.201506182210 [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 So, we should put the newer AngularJS in the EA site. But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: {code} org.eclipse.angularjs.ui_1.0.0.201508312121.jar org.eclipse.angularjs.core_1.0.0.201508312121.jar angularjs-eclipse-feature_1.0.0.201508312121.jar {code} So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:27:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 20 Oct 2015 11:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-507) JBDSIS 8.0.4/ JBTIS 4.2.4 content update In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu closed JBTIS-507. ---------------------------- Resolution: Done CR2 built and sent to QE. > JBDSIS 8.0.4/ JBTIS 4.2.4 content update > ---------------------------------------- > > Key: JBTIS-507 > URL: https://issues.jboss.org/browse/JBTIS-507 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.4.CR1, 4.2.4.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.4.CR1, 4.2.4.CR1 > > > Update component contents for the 8.0.4 Luna release -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:37:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 20 Oct 2015 11:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20954) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Hibernate] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers closed JBIDE-20954. ----------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Hibernate] > ----------------------------------------------------------- > > Key: JBIDE-20954 > URL: https://issues.jboss.org/browse/JBIDE-20954 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Hibernate]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22hibernate%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 11:52:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 11:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120097#comment-13120097 ] Nick Boldt commented on JBIDE-21001: ------------------------------------ Note: ran PR 543 in master branch w/ all tests and this: {code} [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 12:56 min [INFO] Finished at: 2015-10-20T11:39:08-04:00 [INFO] Final Memory: 122M/774M {code} > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 12:40:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 20 Oct 2015 12:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120127#comment-13120127 ] Max Rydahl Andersen commented on JBTIS-523: ------------------------------------------- Are we only talking about the install experience via the installer or overall install of Fuse ? The installer is by far the least used afaics so if we only look at this from installer perspective we will not cover the paths of BYOE (bring your own eclipse) for users using eclipse market place. If just caring about installation could be solved by adding a Fuse specific marketplace entry that just contains the Fuse functionallity as done for the IS marketplace entry. This would still install the required JBDS core parts, incl. central. Is this just about having a way to install it easily or also about how Fuse will be configured in eclipse ? Then setting first perspectives are bad/not enough IMO. Maybe Fuse could add entries to JBoss perspective ? and beyond that is making Fuse quickstarts etc. available from JBoss Central so anyone can get to Fuse even without having first installed Fuse and once installed have access to all the Fuse quickstarts. > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} > Comments welcome! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 12:43:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 20 Oct 2015 12:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120128#comment-13120128 ] Max Rydahl Andersen commented on JBTIS-523: ------------------------------------------- btw. afaics default JBDS 9 JBoss perspective out of the box today have Fuse Integration in the the Perspective list, no need to use "Other...." and Fuse Integration is listed front and center on first start in Central. So not sure setting the default perspective changes much ? > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} > Comments welcome! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120137#comment-13120137 ] Nick Boldt commented on JBIDE-20947: ------------------------------------ As of 2015-10-20 found these root pom versions INCORRECT: {code} aerogear :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT livereload :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT playground :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT server :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT webservices :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT {code} > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:13:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120138#comment-13120138 ] Nick Boldt commented on JBIDE-20957: ------------------------------------ As of 2015-10-20 found these root pom versions INCORRECT: {code} aerogear :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT livereload :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT playground :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT server :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT webservices :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT {code} > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] > ------------------------------------------------------------ > > Key: JBIDE-20957 > URL: https://issues.jboss.org/browse/JBIDE-20957 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22playground%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:13:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20967) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120139#comment-13120139 ] Nick Boldt commented on JBIDE-20967: ------------------------------------ As of 2015-10-20 found these root pom versions INCORRECT: {code} aerogear :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT livereload :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT playground :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT server :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT webservices :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT {code} > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] > ------------------------------------------------------------ > > Key: JBIDE-20967 > URL: https://issues.jboss.org/browse/JBIDE-20967 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [LiveReload]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22livereload%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:14:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20963) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120140#comment-13120140 ] Nick Boldt commented on JBIDE-20963: ------------------------------------ As of 2015-10-20 found these root pom versions INCORRECT: {code} aerogear :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT livereload :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT playground :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT server :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT webservices :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT {code} > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] > ------------------------------------------------------------- > > Key: JBIDE-20963 > URL: https://issues.jboss.org/browse/JBIDE-20963 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Webservices]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22webservices%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:14:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120141#comment-13120141 ] Nick Boldt commented on JBIDE-20948: ------------------------------------ As of 2015-10-20 found these root pom versions INCORRECT: {code} aerogear :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT livereload :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT playground :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT server :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT webservices :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT {code} > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] > ---------------------------------------------------------- > > Key: JBIDE-20948 > URL: https://issues.jboss.org/browse/JBIDE-20948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Aerogear]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22aerogear-hybrid%22%2C%22cordovasim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:14:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20953) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120142#comment-13120142 ] Nick Boldt commented on JBIDE-20953: ------------------------------------ As of 2015-10-20 found these root pom versions INCORRECT: {code} aerogear :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT livereload :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT playground :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT server :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT webservices :: org.jboss.tools parent 4.3.0.Final-SNAPSHOT {code} > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] > -------------------------------------------------------- > > Key: JBIDE-20953 > URL: https://issues.jboss.org/browse/JBIDE-20953 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Server]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22server%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:14:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20951: ---------------------------------- Assignee: Martin Malina > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:17:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120143#comment-13120143 ] Nick Boldt commented on JBIDE-20951: ------------------------------------ Root pom updated to the correct parent pom reference... https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstools-4.3.x/pom.xml#L8 ... but your plugins are still at version 4.3.0, not 4.3.1. Did you ever do a 4.3.0 release, or are you STILL working toward your 4.3.0.Final bits? > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:18:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120143#comment-13120143 ] Nick Boldt edited comment on JBIDE-20951 at 10/20/15 1:17 PM: -------------------------------------------------------------- Root pom updated to the correct parent pom reference... https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstools-4.3.x/pom.xml#L8 ... but your plugins are still at version 4.3.0 [1], not 4.3.1. Did you ever do a 4.3.0 release, or are you STILL working toward your 4.3.0.Final bits, with the latest being 4.3.0.Beta1? [1] http://download.jboss.org/jbosstools/9.0/snapshots/builds/jbosstools-integration-tests.aggregate_4.3.mars/latest/all/repo/plugins/ was (Author: nickboldt): Root pom updated to the correct parent pom reference... https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstools-4.3.x/pom.xml#L8 ... but your plugins are still at version 4.3.0, not 4.3.1. Did you ever do a 4.3.0 release, or are you STILL working toward your 4.3.0.Final bits? > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:33:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Summary: Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:41:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120146#comment-13120146 ] Nick Boldt commented on JBIDE-20993: ------------------------------------ I put these in place to mirror what's on https://devstudio.redhat.com -- * https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars * https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS. But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0. This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing. -- Would you be happy if instead of a /10.0 folder we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder. > http://download.jboss.org/jbosstools/ contains wrong versions > ------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:42:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120146#comment-13120146 ] Nick Boldt edited comment on JBIDE-20993 at 10/20/15 1:41 PM: -------------------------------------------------------------- I put these in place to mirror what's on https://devstudio.redhat.com -- * https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars * https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS. But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0. This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. I don't recall if there was an announcement about this since I considered it simply a releng thing not worthy of announcement. And "under the covers" change, if you will. While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing. -- Would you be happy if instead of a /10.0 folder we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder. was (Author: nickboldt): I put these in place to mirror what's on https://devstudio.redhat.com -- * https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars * https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS. But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0. This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing. -- Would you be happy if instead of a /10.0 folder we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder. > http://download.jboss.org/jbosstools/ contains wrong versions > ------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:46:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 13:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120146#comment-13120146 ] Nick Boldt edited comment on JBIDE-20993 at 10/20/15 1:45 PM: -------------------------------------------------------------- I put these in place to mirror what's on https://devstudio.redhat.com -- * https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars * https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS. But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0. This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. I don't recall if there was an announcement about this since I considered it simply a releng thing not worthy of announcement. And "under the covers" change, if you will. While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing. -- Would you be happy if instead of a /10.0/ folder for JBDS, we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder. Thus we would publish to URLs like these: {quote} https://devstudio.redhat.com/neon/snapshots/builds/ https://devstudio.redhat.com/neon/snapshots/updates/ https://devstudio.redhat.com/neon/staging/builds/ https://devstudio.redhat.com/neon/staging/updates/ and http://download.jboss.org/jbosstools/neon/snapshots/builds/ http://download.jboss.org/jbosstools/neon/snapshots/updates/ http://download.jboss.org/jbosstools/neon/staging/builds/ http://download.jboss.org/jbosstools/neon/staging/updates/ {quote} instead of {quote} https://devstudio.redhat.com/10.0/snapshots/builds/ https://devstudio.redhat.com/10.0/snapshots/updates/ https://devstudio.redhat.com/10.0/staging/builds/ https://devstudio.redhat.com/10.0/staging/updates/ and http://download.jboss.org/jbosstools/neon/snapshots/builds/ http://download.jboss.org/jbosstools/neon/snapshots/updates/ http://download.jboss.org/jbosstools/neon/staging/builds/ http://download.jboss.org/jbosstools/neon/staging/updates/ {quote} (Of course there would also be similar URLs with /development/ and /stable/ in future.) was (Author: nickboldt): I put these in place to mirror what's on https://devstudio.redhat.com -- * https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars * https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS. But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0. This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. I don't recall if there was an announcement about this since I considered it simply a releng thing not worthy of announcement. And "under the covers" change, if you will. While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing. -- Would you be happy if instead of a /10.0 folder we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder. > http://download.jboss.org/jbosstools/ contains wrong versions > ------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:48:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 13:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20531: ---------------------------------- Attachment: Service and routing page.png > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-20531 > URL: https://issues.jboss.org/browse/JBIDE-20531 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > Attachments: Service and routing page.png > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 13:49:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 13:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-20531: ---------------------------------- Attachment: service port edit dialog.png > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-20531 > URL: https://issues.jboss.org/browse/JBIDE-20531 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > Attachments: Service and routing page.png, service port edit dialog.png > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 14:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 14:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ symlinks Eclipse versions to JBDS versions for release engineering convenience In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20993: ------------------------------- Summary: http://download.jboss.org/jbosstools/ symlinks Eclipse versions to JBDS versions for release engineering convenience (was: http://download.jboss.org/jbosstools/ contains wrong versions) > http://download.jboss.org/jbosstools/ symlinks Eclipse versions to JBDS versions for release engineering convenience > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 14:08:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 14:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20993: ------------------------------- Summary: http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions (was: http://download.jboss.org/jbosstools/ symlinks Eclipse versions to JBDS versions for release engineering convenience) > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 15:06:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 20 Oct 2015 15:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-523: ----------------------------- Description: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart JBDS comes up in the Fuse Integration perspective - read to go. {code} Comments welcome! was: The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. Here's a usability scenario targeting Fuse Tooling: {code} Test scenario A: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` 4. Select the Software/Update tab in the JBoss Central view. 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. Select the following item: JBoss Fuse Development 7. Accept/ respond 'Yes' and restart 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario B: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario C: 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration ----------------------------------------------------------------------------- Test scenario D: (future - not available currently) 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer 5. Accept/ respond 'Yes' and restart JBDS comes up in the Fuse Integration perspective - read to go. {code} Comments welcome! > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} > Comments welcome! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 15:10:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 20 Oct 2015 15:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120182#comment-13120182 ] Paul Leacu commented on JBTIS-523: ---------------------------------- Yes - no need to select 'Other...' - I've corrected the test instructions. I'll let these guys speak for themselves but I believe they want to run an installer and be left on restart in the Fuse Integration perspective - ready to go. Basically led by the hand into the Fuse tooling environment. It's certainly trivial to select the perspective but they'd like to eliminate any place the user could get lost. > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} > Comments welcome! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 15:56:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Tue, 20 Oct 2015 15:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker reassigned JBIDE-20990: ----------------------------------- Assignee: Rob Stryker > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 16:14:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 20 Oct 2015 16:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120203#comment-13120203 ] Alexey Kazakov commented on JBIDE-21001: ---------------------------------------- Go ahead with updating discovery. But we want to keep angularjs in jst/pom.xml to have it available when running tests. There are not direct dependencies but we should make sure our tests pass when angularJS is installed. > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 16:14:05 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 20 Oct 2015 16:14:05 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-21001: -------------------------------------- Assignee: Nick Boldt (was: Alexey Kazakov) > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 16:54:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 16:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: Jeff Cantrill created JBIDE-21002: ------------------------------------- Summary: Expose additional service ports from deploy docker image wizard Key: JBIDE-21002 URL: https://issues.jboss.org/browse/JBIDE-21002 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Fix For: 4.3.1.Beta1 Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image * Also only remove those which were added * Only reset those which are defaults * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 16:54:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 16:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-21002: ---------------------------------- Affects Version/s: 4.4.0.Alpha1 (was: 4.3.0.CR1) > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-21002 > URL: https://issues.jboss.org/browse/JBIDE-21002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 16:56:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 16:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill updated JBIDE-21002: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-21002 > URL: https://issues.jboss.org/browse/JBIDE-21002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.4.0.Alpha1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 16:59:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Tue, 20 Oct 2015 16:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill resolved JBIDE-21002. ----------------------------------- Resolution: Done cherry-picked into master: 66ace82c1813e8f6f92015b84e5e595906cd55bf > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-21002 > URL: https://issues.jboss.org/browse/JBIDE-21002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.4.0.Alpha1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 17:22:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 20 Oct 2015 17:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120227#comment-13120227 ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- I saw it before but thought it was a failed cross publish since some jira mentioned that had occurred. Didn't connect the dots before talking with [~dgolovin] which was mentioning how confusing download.jboss.org continues to be, even after we cleaned up for this latest GA. Thus it is not under the covers, it is misleading. I thus suggest to please remove it asap since nothing in our system should rely on v9 or v10 for tools.jboss.org - that is simply just wrong. About having ability to share scripts - I don't follow why it is a problem that you just have one property/variable that is called "stream" (for example) which on jbds is set to /9.0 and /10.0 then in scripts the *only* think you worry about is what the value of "stream" is. Nothing should have to care about it being either neon, mars, 9.0 or 10.0 - no meaning should be giving to this besides "stream". If such things exist today, please point to it to explain, otherwise please remove it on download.jboss.org. About having neon/mars on devstudio.redhat.com - that is definitely much better since it is not conflicting terms; but why create this redundancy of urls when (at least from my POV) there should never be anything that need to know what specific stream we are referring to outside a "stream" variable ? > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 17:25:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 20 Oct 2015 17:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120228#comment-13120228 ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- i.e. in your example above I don't see it as wanting explicit values I see it much more abstract: {code} ${streamurl}/snapshots/builds/ ${streamurl}/snapshots/updates/ ${streamurl}/staging/builds/ ${streamurl}/staging/updates/ {code} and dependent on we doing jboss tools or devstudio $streamurl could be pointing to completely arbitrary urls allowing us to even publish to localhost if we wanted to. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 17:31:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 20 Oct 2015 17:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120229#comment-13120229 ] Max Rydahl Andersen commented on JBTIS-523: ------------------------------------------- If the Fuse perspective would actually have the editor area default available so Central should show up which actually can guide/help the user then i don't see much problems. EVeryone just need to be aware this will only work for the Fuse Installer, not for everywhere else users will install from. This is why I think the idea we've talked about in the past to actually have Central know about what kind of user your are and reorder its wizards/quickstarts based on your priorities/profile. i.e. are you a 80% Fuse 20% EAP then you dont get to see Teiid, or if you are 100% Teiid then all EAP and Fuse is shown last if at all. But even before that - make Fuse quickstarts available from central. That would be much better since Fuse IDE don't support multiple versions of quickstarts, but central does. > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto2.jar > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} > Comments welcome! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 18:22:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Tue, 20 Oct 2015 18:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker reassigned JBIDE-20947: ----------------------------------- Assignee: Rob Stryker > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 18:27:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Tue, 20 Oct 2015 18:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20953) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker closed JBIDE-20953. ------------------------------- Resolution: Done done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server] > -------------------------------------------------------- > > Key: JBIDE-20953 > URL: https://issues.jboss.org/browse/JBIDE-20953 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Server]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22server%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 19:02:00 2015 From: issues at jboss.org (Gorkem Ercan (JIRA)) Date: Tue, 20 Oct 2015 19:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gorkem Ercan closed JBIDE-20948. -------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] > ---------------------------------------------------------- > > Key: JBIDE-20948 > URL: https://issues.jboss.org/browse/JBIDE-20948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Aerogear]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22aerogear-hybrid%22%2C%22cordovasim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 21:54:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 20 Oct 2015 21:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120251#comment-13120251 ] Nick Boldt commented on JBIDE-21001: ------------------------------------ But the tests don't cause the installation of the angularJS feature or plugins. The update site doesn't include them either. Can you show me where ANYTHING in jbosstools-jst actually requires, depends, references, or smiles in the direction of the AngularJS stuff? I can't see it. :( > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 02:56:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Wed, 21 Oct 2015 02:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated JBDS-3516: ---------------------------- Sprint: 12-Oct >> 25-Oct 2015-JBDS/JBT Added to current sprint and drafting this information in google docs. Will paste the link here for review soon. > Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim] > ------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3516 > URL: https://issues.jboss.org/browse/JBDS-3516 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, documentation, updatesite > Affects Versions: 9.0.0.CR1 > Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100 > jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0.0.CR1-updatesite-central.zip > Reporter: Jan Richter > Assignee: Misha Ali > Fix For: 9.0.1.Beta1 > > > This is what comes up when I try to install everything from the central zip: > {noformat} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28) > To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 03:23:01 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Wed, 21 Oct 2015 03:23:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20967) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon closed JBIDE-20967. --------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload] > ------------------------------------------------------------ > > Key: JBIDE-20967 > URL: https://issues.jboss.org/browse/JBIDE-20967 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [LiveReload]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22livereload%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 03:42:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Wed, 21 Oct 2015 03:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20963) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Coulon closed JBIDE-20963. --------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices] > ------------------------------------------------------------- > > Key: JBIDE-20963 > URL: https://issues.jboss.org/browse/JBIDE-20963 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Webservices]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22webservices%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 03:51:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Wed, 21 Oct 2015 03:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120292#comment-13120292 ] Martin Malina commented on JBIDE-20951: --------------------------------------- [~nickboldt], how about this? :) https://github.com/jbosstools/jbosstools-integration-tests/pull/1210 > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 04:41:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 21 Oct 2015 04:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120321#comment-13120321 ] Max Rydahl Andersen commented on JBIDE-20976: --------------------------------------------- I understand the use of M2 is to ensure we at least have the eclipse platform version higher than our previous release. What is the reason for updating angularjs ? Have it been requested and verified it does not break our current integration or is this update to perform that work/test ? > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 05:11:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Wed, 21 Oct 2015 05:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20997) Should not be able to create duplicative labels In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20997: ---------------------------------- Description: User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. (was: User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name. But as a result only the last one is created (it looks like others are either ignored or overwrite). It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label.) > Should not be able to create duplicative labels > ----------------------------------------------- > > Key: JBIDE-20997 > URL: https://issues.jboss.org/browse/JBIDE-20997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Mari?n Labuda > > User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 07:25:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 21 Oct 2015 07:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20978) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20978: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # ASSERT: have a freshly launched Eclipse # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. was: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 07:42:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 21 Oct 2015 07:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-524) Update SAP tooling to 7.3.2 In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-524: --------------------------------------- Summary: Update SAP tooling to 7.3.2 Key: JBTIS-524 URL: https://issues.jboss.org/browse/JBTIS-524 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 8.0.4.CR2 Reporter: Andrej Podhradsky Priority: Blocker JBDS-IS 8.0.4.CR2 contains Fuse tooling 7.3.2.v20151008-1250-H108-CR2 but SAP tooling is in version 7.3.0.v20150622-1535-H9-Final. Please create a new build of SAP tooling and add it to https://devstudio.redhat.com/updates/8.0/integration-stack/extras -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 07:56:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 21 Oct 2015 07:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-490) Use the extras plugins update site 'extras' for SAP. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-490. ----------------------------------- Verified with JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR2 (also works with JBDS-IS 8.0.3.GA). > Use the extras plugins update site 'extras' for SAP. > ---------------------------------------------------- > > Key: JBTIS-490 > URL: https://issues.jboss.org/browse/JBTIS-490 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.3.GA, 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.3.GA > > > We currently have this: > https://devstudio.redhat.com/updates/8.0/integration-stack/jboss-fuse-sap-tool-suite/ > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/jboss-fuse-sap-tool-suite/ > what we want is this: > https://devstudio.redhat.com/updates/8.0/integration-stack/extras > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/extras/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:25:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Wed, 21 Oct 2015 08:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed JBIDE-20951. --------------------------------- Release Notes Text: PR merged -> version bumped to 4.3.1-SNAPSHOT. And repo can be built with the new TP. All the rest is done, too. Closing. Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:25:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Wed, 21 Oct 2015 08:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina updated JBIDE-20951: ---------------------------------- Release Notes Text: (was: PR merged -> version bumped to 4.3.1-SNAPSHOT. And repo can be built with the new TP. All the rest is done, too. Closing.) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:25:01 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Wed, 21 Oct 2015 08:25:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Malina closed JBIDE-20951. --------------------------------- Resolution: Done PR merged -> version bumped to 4.3.1-SNAPSHOT. And repo can be built with the new TP. All the rest is done, too. Closing. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22qa%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 09:16:02 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 21 Oct 2015 09:16:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20530) Add docker image lookup to deploy image wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill reassigned JBIDE-20530: ------------------------------------- Assignee: Jeff Cantrill > Add docker image lookup to deploy image wizard > ---------------------------------------------- > > Key: JBIDE-20530 > URL: https://issues.jboss.org/browse/JBIDE-20530 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Add a way to lookup a docker image from deploy an image wizard instead of just freeform text -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 09:27:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 21 Oct 2015 09:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-514) Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-514. ------------------------------ Fix Version/s: 4.3.1.Beta1 Resolution: Done Removed erroneous category setting https://github.com/jbosstools/jbosstools-integration-stack/commit/c6254f55a1a94fb2c921fb3a57fbd5ef1065c530 > Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central > ------------------------------------------------------------------------------------------------- > > Key: JBTIS-514 > URL: https://issues.jboss.org/browse/JBTIS-514 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Environment: jee-mars-1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 4.3.1.Beta1 > > > After installing BYOE into Eclipse Mars JEE and installing integration tools I got the following error in Error Log > Unknown category 'org.jboss.tools.discovery.certification.supported' referenced by connector 'org.jboss.runtime.drools.detector.feature' declared in org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20151006_1928_B438.jar_7070743946524519340.jar > The eclipse instance was run as follows > {code} > ./eclipse -vmargs \ > -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ > -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery \ > -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/earlyaccess > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 09:28:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 21 Oct 2015 09:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-502) Include Drools tooling 6.3 to JBDS-IS 9.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-502. ------------------------------ Fix Version/s: 9.0.1.Beta1 4.3.1.Beta1 Resolution: Done Updated drools https://github.com/jbosstools/jbosstools-integration-stack/commit/c6254f55a1a94fb2c921fb3a57fbd5ef1065c530 > Include Drools tooling 6.3 to JBDS-IS 9.x > ----------------------------------------- > > Key: JBTIS-502 > URL: https://issues.jboss.org/browse/JBTIS-502 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1, 4.3.1.Beta1 > > > There is a new version of Drools tooling which is available at http://drools.org/download/download.html > Please include the new Drools tooling to the next build of JBDS-IS 9.x -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 09:30:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 21 Oct 2015 09:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-524) Update SAP tooling to 7.3.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-524: -------------------------------- Assignee: Paul Leacu > Update SAP tooling to 7.3.2 > --------------------------- > > Key: JBTIS-524 > URL: https://issues.jboss.org/browse/JBTIS-524 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.4.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > JBDS-IS 8.0.4.CR2 contains Fuse tooling 7.3.2.v20151008-1250-H108-CR2 but SAP tooling is in version 7.3.0.v20150622-1535-H9-Final. > Please create a new build of SAP tooling and add it to https://devstudio.redhat.com/updates/8.0/integration-stack/extras -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 09:33:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 21 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-525) Ineligible update sites after installing SAP tooling In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-525: --------------------------------------- Summary: Ineligible update sites after installing SAP tooling Key: JBTIS-525 URL: https://issues.jboss.org/browse/JBTIS-525 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.4.CR2 Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR2 Reporter: Andrej Podhradsky After installing SAP tooling there are ineligible update sites related to jbosstools, see the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 09:34:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Wed, 21 Oct 2015 09:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-525) Ineligible update sites after installing SAP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-525: ------------------------------------ Attachment: after_installing_sap.png > Ineligible update sites after installing SAP tooling > ---------------------------------------------------- > > Key: JBTIS-525 > URL: https://issues.jboss.org/browse/JBTIS-525 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.4.CR2 > Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR2 > Reporter: Andrej Podhradsky > Attachments: after_installing_sap.png > > > After installing SAP tooling there are ineligible update sites related to jbosstools, see the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 09:55:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 21 Oct 2015 09:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-524) Update SAP tooling to 7.3.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-524. ------------------------------ Fix Version/s: 8.0.4.CR2 Resolution: Done SAP devstudio updated. > Update SAP tooling to 7.3.2 > --------------------------- > > Key: JBTIS-524 > URL: https://issues.jboss.org/browse/JBTIS-524 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.4.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.4.CR2 > > > JBDS-IS 8.0.4.CR2 contains Fuse tooling 7.3.2.v20151008-1250-H108-CR2 but SAP tooling is in version 7.3.0.v20150622-1535-H9-Final. > Please create a new build of SAP tooling and add it to https://devstudio.redhat.com/updates/8.0/integration-stack/extras -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 10:22:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 21 Oct 2015 10:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-20957: ---------------------------------- Assignee: Alexey Kazakov (was: Mickael Istria) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] > ------------------------------------------------------------ > > Key: JBIDE-20957 > URL: https://issues.jboss.org/browse/JBIDE-20957 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22playground%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 10:22:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 21 Oct 2015 10:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120549#comment-13120549 ] Nick Boldt commented on JBIDE-20957: ------------------------------------ Since [~mickael_istria] is on PTO, could you review & apply these PRs, [~akazakov] ? > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] > ------------------------------------------------------------ > > Key: JBIDE-20957 > URL: https://issues.jboss.org/browse/JBIDE-20957 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22playground%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 10:31:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 10:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120560#comment-13120560 ] Alexey Kazakov commented on JBIDE-20957: ---------------------------------------- Ah, I forgot that Mickael is on PTO, will do, thank you Nick! > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] > ------------------------------------------------------------ > > Key: JBIDE-20957 > URL: https://issues.jboss.org/browse/JBIDE-20957 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22playground%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 11:10:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 21 Oct 2015 11:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-525) Ineligible update sites after installing SAP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu updated JBTIS-525: ----------------------------- Priority: Blocker (was: Major) > Ineligible update sites after installing SAP tooling > ---------------------------------------------------- > > Key: JBTIS-525 > URL: https://issues.jboss.org/browse/JBTIS-525 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.4.CR2 > Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR2 > Reporter: Andrej Podhradsky > Priority: Blocker > Attachments: after_installing_sap.png > > > After installing SAP tooling there are ineligible update sites related to jbosstools, see the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 11:29:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 21 Oct 2015 11:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120606#comment-13120606 ] Nick Boldt commented on JBIDE-20976: ------------------------------------ Re: angular update, see JBIDE-21001 where we discuss the fact that the version used when building jbosstools-jst for 4.3.0.Final is NOT the version that was included in the Early Access site for 4.3.0.Final. That mismatch needs to be corrected. > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 11:41:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 11:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20997) Should not be able to create duplicative labels In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20997: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Should not be able to create duplicative labels > ----------------------------------------------- > > Key: JBIDE-20997 > URL: https://issues.jboss.org/browse/JBIDE-20997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Mari?n Labuda > Fix For: 4.4.0.Alpha1 > > > User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:14:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 12:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20565) Do not display OpenShift v2/v3 but rather OpenShift 2/3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-20565. --------------------------------- Resolution: Done Fixed in master/4.3.x > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-20565 > URL: https://issues.jboss.org/browse/JBIDE-20565 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:21:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 21 Oct 2015 12:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120644#comment-13120644 ] Nick Boldt commented on JBIDE-20993: ------------------------------------ You misunderstand me. I was suggesting that instead of using: * /mars/ and /neon/ for JBT and * /9.0/ and /10.0/ for JBDS (see how they're different?) we could instead use: * /mars/ and /neon/ for JBT and * /mars/ and /neon/ for JBDS (see how they're the same?). So, no more symlinks would be needed, since it'd be the same path segment on both servers. That said, obviously the stable URL for JBDS 9 would have to stay as https://devstudio.redhat.com/9.0/stable/updates/ But we could have this for JBDS 10: https://devstudio.redhat.com/neon/stable/updates/ https://devstudio.redhat.com/neon/development/updates/ https://devstudio.redhat.com/neon/staging/updates/ https://devstudio.redhat.com/neon/snapshots/updates/ which would map nicely to the URLs for JBT 4.4: http://download.jboss.org/jbosstools/neon/stable/updates/ http://download.jboss.org/jbosstools/neon/development/updates/ http://download.jboss.org/jbosstools/neon/staging/updates/ http://download.jboss.org/jbosstools/neon/snapshots/updates/ -- As to where/how I have scripts which require a different variable depending on which product is being published/released, well, here's an example: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/pom.xml#L154 (uses devstudioReleaseVersion = 10.0) vs. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/pom.xml#L196 (uses eclipseReleaseName = neon) If they both used *eclipseReleaseName* in the path, there'd be fewer places to have the code deviate. Similarly the release guide for JBT/JBDS, pushing bits to (or from staging) uses nearly-identical scriptlets to copy bits around. But to further automate that via an actual script, we need more synchronicity between the releases so less things are different and the same script can be used for multiple purposes. Thus a script like https://github.com/jbosstools/jbosstools-build-ci/pull/137/files could simply use `-eclipseReleaseName neon` instead of needing a different path segment for JBDS. --- So, TL;DR: are you cool with these URLs for JBDS 10? Or do you need to see a /10.0/ path segment in there instead of /neon/ (cc: [~akazakov] ) ? https://devstudio.redhat.com/neon/stable/updates/ https://devstudio.redhat.com/neon/development/updates/ https://devstudio.redhat.com/neon/staging/updates/ https://devstudio.redhat.com/neon/snapshots/updates/ > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 12:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20957. ---------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] > ------------------------------------------------------------ > > Key: JBIDE-20957 > URL: https://issues.jboss.org/browse/JBIDE-20957 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22playground%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 12:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20947: -------------------------------------- Assignee: Nick Boldt (was: Rob Stryker) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:44:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Wed, 21 Oct 2015 12:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 In-Reply-To: References: Message-ID: Jeff Cantrill created JBIDE-21003: ------------------------------------- Summary: Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 Key: JBIDE-21003 URL: https://issues.jboss.org/browse/JBIDE-21003 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.3.x Reporter: Jeff Cantrill *Reason:* update linuxtools.docker to expose ImageSearch wizard *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 *Version:* .... *License and owner:* ... *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ *JBoss mirror:* Leave empty *Include Sources:* Yes *Affected JBoss Tools components:* jbosstools-openshift *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} If applicable: *non-p2 repository:* ... *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:48:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 12:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21003: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 Docker Tools 4.2.0 is targeting Mars, correct? [~xcoulon]? > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:48:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 12:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-21003: -------------------------------------- Assignee: Nick Boldt > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:49:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 21 Oct 2015 12:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120664#comment-13120664 ] Nick Boldt commented on JBIDE-21001: ------------------------------------ New PRs to show how jbosstools-jst could depend on the EA TP (which contains 3rd party stuff only). Note that the EA TP is currently ONLY AngularJS but some day it could contain more. (It used to also contain Tern.) https://github.com/jbosstools/jbosstools-jst/pull/544 https://github.com/jbosstools/jbosstools-jst/pull/545 Note the fluffed up instructions and comments -- think people might see it this way? :D > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:55:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 21 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120670#comment-13120670 ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- I completely get what you mean. I opened the jira to get the misleading 9.0 and 10.0 folders removed ASAP. Can we get that fixed independent on what scripts optimizations you might want to do in future ? I don't see whether you use neon or 10.0 that this changes anything. You still need *one* variable for the stream. Whether that is called 10.0 or neon should not change anything. The exact same number segments are there - I simply do not get why it matters if one is 10.0 or neon nor why you need symlinks for this. Your scripts just need one thing 10.0 neon And you then use ${stream} in the locations that needs this separated out. then there are zero differences, except exact same difference that you need devstudio.redhat.com in one, and download.jboss.org in another. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 12:59:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 21 Oct 2015 12:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120672#comment-13120672 ] Nick Boldt commented on JBIDE-20993: ------------------------------------ /me asks direct question, about shell scripting & maven variables to drive deployment /you answer a different one, about ant scripting *sigh* I will remove the symlinks on download.jboss.org and assume you are OK with keeping them on devstudio.redhat.com. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 13:01:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 21 Oct 2015 13:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120672#comment-13120672 ] Nick Boldt edited comment on JBIDE-20993 at 10/21/15 1:00 PM: -------------------------------------------------------------- /me asks direct question, about shell scripting & maven variables to drive deployment /you answer a different one, about ant scripting /me sighs I have removed these symlinks: http://download.jboss.org/jbosstools/9.0 http://download.jboss.org/jbosstools/10.0 I will further assume you are OK with keeping the mars and neon symlinks on devstudio.redhat.com. was (Author: nickboldt): /me asks direct question, about shell scripting & maven variables to drive deployment /you answer a different one, about ant scripting *sigh* I will remove the symlinks on download.jboss.org and assume you are OK with keeping them on devstudio.redhat.com. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 13:46:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 21 Oct 2015 13:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120683#comment-13120683 ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- I did not answer anything about ant or maven scripting. I gave examples of variable declaration in general - this issue applies to both maven, shell and ant etc. And no, the same issue apply to devstudio.redhat.com. Reasons why having 10.0 on devstudio and neon on download.jboss.org is a Good Thing: #1 It is very clear if some publishing went wrong. If 10.0 shows up on download.jboss.org or neon on devstudio.redhat.com we know something got messed up. #2 You do not need to have the full hostname to know what kind of deployment we are looking at. #3 10.0 is the actual version of the product so it has a much clearer meaning to users than Neon. Yes, you could argue then we should use version numbers on jboss tools community - but then see reason #1 And no matter if we use maven, ant or shell - none of this matters if the abstraction in property names are which release stream are being referenced, as opposed to devstudioVersion or eclipseBase. So in short - no advantages to having the exact same for this base path (I 100% agree the further sub paths which we constantly publish/update are good to have aligned), but at lest 3 advantages to have a different base path. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 13:48:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 21 Oct 2015 13:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120685#comment-13120685 ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- btw. what I suggest above is what is used in the jenkins templating. Pretty simple IMO to just abstract this away. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 15:07:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 15:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20717) Inconsistent upper casing in New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-20717. --------------------------------- Assignee: Fred Bricon Resolution: Done Fixed in master/4.3.x > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-20717 > URL: https://issues.jboss.org/browse/JBIDE-20717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.Beta1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 15:07:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 15:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21004) Inconsistent upper casing in New Connection dialog In-Reply-To: References: Message-ID: Fred Bricon created JBIDE-21004: ----------------------------------- Summary: Inconsistent upper casing in New Connection dialog Key: JBIDE-21004 URL: https://issues.jboss.org/browse/JBIDE-21004 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Mari?n Labuda Assignee: Fred Bricon Priority: Minor Fix For: 4.3.1.Beta1 There are several places, where upper casing should be more consistent. Label for a default server checkbox is "Use default Server". I think better would be "Use default server" Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 15:07:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 15:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21004) Inconsistent upper casing in New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-21004: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-21004 > URL: https://issues.jboss.org/browse/JBIDE-21004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 15:08:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 15:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21004) Inconsistent upper casing in New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-21004. --------------------------------- Resolution: Done Fixed in master > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-21004 > URL: https://issues.jboss.org/browse/JBIDE-21004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 15:54:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Wed, 21 Oct 2015 15:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20977) XML identation size is not editable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120714#comment-13120714 ] Snjezana Peco commented on JBIDE-20977: --------------------------------------- This is a gtk3 bug. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=428246 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=480335. > XML identation size is not editable > ----------------------------------- > > Key: JBIDE-20977 > URL: https://issues.jboss.org/browse/JBIDE-20977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1b, Eclipse 4.4 > I have Fedora 19, Java 1.7_60, Gnome3, it is both case for JBDS 8.x and Eclipse 4.4 > Colleague of mine has RHEL7 with Gnome, tested on JBDS 8.x as well. > Reporter: Stefan Miklosovic > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: xml-preferences.png > > > !xml-preferences.png! > Window -> Preferencies -> XML -> XML Files -> Editor > Ident using spaces is checked. > Identation size field is not editable, there is still "1" in it. Clicking at arrows (or + - buttons) does not work. I can not rise it to 4 spaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 17:28:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 17:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21005) Node location should point to the node executable file instead of the parent folder of it In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-21005: -------------------------------------- Summary: Node location should point to the node executable file instead of the parent folder of it Key: JBIDE-21005 URL: https://issues.jboss.org/browse/JBIDE-21005 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: javascript, javascript-bower Affects Versions: 4.3.0.Final Reporter: Alexey Kazakov Assignee: Ilya Buziuk Fix For: 3.3.x, 4.4.0.Alpha1 Window->Preferences->Java Script tools->Node It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 17:29:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 17:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21005) Node location should point to the node executable file instead of the parent folder of it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21005: ----------------------------------- Fix Version/s: (was: 3.3.x) > Node location should point to the node executable file instead of the parent folder of it > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 17:31:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 21 Oct 2015 17:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120739#comment-13120739 ] Rob Stryker commented on JBIDE-20990: ------------------------------------- When using the terminal view to launch vagrant up, there are lots of errors if your environment variables include bash functions. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=469184 > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 17:34:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 21 Oct 2015 17:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120741#comment-13120741 ] Rob Stryker commented on JBIDE-20996: ------------------------------------- The downloadruntimes api doesn't currently have any ability for dl-rt providers to actually provide feedback or custom logic =/ this would require some api extensions, and they'd have to be carefully considered so as not to just be a band-aid solution that fixes only one usecase. Such band-aids that add api for only one use-case tend to lead to cluttered code later on if repeated several times. > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 18:12:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 21 Oct 2015 18:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20978) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120746#comment-13120746 ] Andre Dietisheim commented on JBIDE-20978: ------------------------------------------ merged and pushed to upstream/jbosstools-4.3.x > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 18:13:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 21 Oct 2015 18:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21006) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-21006: ---------------------------------------- Summary: Connection wizard: switching to resets token but form is still valid Key: JBIDE-21006 URL: https://issues.jboss.org/browse/JBIDE-21006 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.3.1.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 18:13:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 21 Oct 2015 18:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21006) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21006: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-21006 > URL: https://issues.jboss.org/browse/JBIDE-21006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 18:15:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Wed, 21 Oct 2015 18:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21006) Connection wizard: switching to resets token but form is still valid In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120748#comment-13120748 ] Andre Dietisheim commented on JBIDE-21006: ------------------------------------------ merged and pushed to upstream/master > Connection wizard: switching to resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-21006 > URL: https://issues.jboss.org/browse/JBIDE-21006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 18:15:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 18:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20507) Remove cursor from a retrieve token styled text In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20507: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.Beta1) > Remove cursor from a retrieve token styled text > ----------------------------------------------- > > Key: JBIDE-20507 > URL: https://issues.jboss.org/browse/JBIDE-20507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Priority: Minor > Fix For: 4.4.x > > > In a New Connection dialog there is a styled text with link "Enter a token or retrieve a new one." Problem is that styled text contains cursor. Cursor is shown on a position after clicking on the position inside the styled text. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 18:28:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 18:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120750#comment-13120750 ] Alexey Kazakov commented on JBIDE-21001: ---------------------------------------- Thanks [~nickboldt] for the PRs. I rebased and merged the 544 (master) but now I'm actually not sure we should use the EA site there. I like the idea to use the real EA site to download angularJS plugins for our tests. If we have incorrect version of angular then the test won't build. But we use different EA TPs during development and production and we should the correct one all the time in the pom.xml. So this approach will require frequent updates of the pom.xml, won't it? I also created two more PRs https://github.com/jbosstools/jbosstools-jst/pull/546 https://github.com/jbosstools/jbosstools-jst/pull/547 to include angularjs plugins to the test environment. But we can't push them before https://github.com/jbosstools/jbosstools-discovery/pull/316 because currently the EA site has an old angularjs plugins 0.10.0 instead of the required 1.0 > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 18:29:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 21 Oct 2015 18:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21001: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/542, https://github.com/jbosstools/jbosstools-jst/pull/543, https://github.com/jbosstools/jbosstools-jst/pull/546, https://github.com/jbosstools/jbosstools-jst/pull/547, https://github.com/jbosstools/jbosstools-discovery/pull/316, https://github.com/jbosstools/jbosstools-discovery/pull/315 (was: https://github.com/jbosstools/jbosstools-jst/pull/542, https://github.com/jbosstools/jbosstools-jst/pull/543, https://github.com/jbosstools/jbosstools-discovery/pull/316/files#diff-90b990031d67570ec413035ac95c400dR7, https://github.com/jbosstools/jbosstools-discovery/pull/315) > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 22:04:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 21 Oct 2015 22:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20715) Add validation for a project name in case of duplicates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20715: ----------------------------------- Assignee: Fred Bricon > Add validation for a project name in case of duplicates > ------------------------------------------------------- > > Key: JBIDE-20715 > URL: https://issues.jboss.org/browse/JBIDE-20715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Fred Bricon > Priority: Optional > Fix For: 4.3.1.Beta1 > > > There could be a simple validation of a project name for duplicates. It should not be necessary to hit Finish button in Create OpenShift Project dialog to find out that project already exists based on response from server. Simple validation based on existence of a tree item of project or some similar mechanism would be helpful. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 01:39:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 22 Oct 2015 01:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21007) Do not display OpenShift v2/v3 but rather OpenShift 2/3 In-Reply-To: References: Message-ID: Mari?n Labuda created JBIDE-21007: ------------------------------------- Summary: Do not display OpenShift v2/v3 but rather OpenShift 2/3 Key: JBIDE-21007 URL: https://issues.jboss.org/browse/JBIDE-21007 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Fred Bricon Assignee: Nick Boldt Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 01:39:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 22 Oct 2015 01:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21007) Do not display OpenShift v2/v3 but rather OpenShift 2/3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-21007: ---------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-21007 > URL: https://issues.jboss.org/browse/JBIDE-21007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 01:39:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 22 Oct 2015 01:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21007) Do not display OpenShift v2/v3 but rather OpenShift 2/3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda resolved JBIDE-21007. ----------------------------------- Resolution: Done > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-21007 > URL: https://issues.jboss.org/browse/JBIDE-21007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 01:39:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 22 Oct 2015 01:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20565) Do not display OpenShift v2/v3 but rather OpenShift 2/3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Labuda updated JBIDE-20565: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-20565 > URL: https://issues.jboss.org/browse/JBIDE-20565 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 02:25:00 2015 From: issues at jboss.org (Chunyun Chen (JIRA)) Date: Thu, 22 Oct 2015 02:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21008) [origin_intservice_49] Can not add/edit service port In-Reply-To: References: Message-ID: Chunyun Chen created JBIDE-21008: ------------------------------------ Summary: [origin_intservice_49] Can not add/edit service port Key: JBIDE-21008 URL: https://issues.jboss.org/browse/JBIDE-21008 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 Reporter: Chunyun Chen Attachments: service_port_screenshot.png It can not add/edit service port on "Services & Routing settings" wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 02:26:00 2015 From: issues at jboss.org (Chunyun Chen (JIRA)) Date: Thu, 22 Oct 2015 02:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21008) [origin_intservice_49] Can not add/edit service port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chunyun Chen updated JBIDE-21008: --------------------------------- Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 OS: Fedora 17 was:OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > [origin_intservice_49] Can not add/edit service port > ---------------------------------------------------- > > Key: JBIDE-21008 > URL: https://issues.jboss.org/browse/JBIDE-21008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 > Reporter: Chunyun Chen > Labels: app, openshift_v3 > Attachments: service_port_screenshot.png > > > It can not add/edit service port on "Services & Routing settings" wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 03:42:00 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Thu, 22 Oct 2015 03:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120797#comment-13120797 ] Xavier Coulon commented on JBIDE-21003: --------------------------------------- [~akazakov] Docker Tools 1.2.0 is what we plan for end of year, so yes, it is targetting Eclipse Mars. I'm not sure there'll be a full release of Linux Tools (4.2.0) or just the Docker tooling component. > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 04:41:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Thu, 22 Oct 2015 04:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21005) Node location should point to the node executable file instead of the parent folder of it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120833#comment-13120833 ] Ilya Buziuk commented on JBIDE-21005: ------------------------------------- Yeah, this is a good idea indeed. Actually I was also thinking about this enhancement. Basically, my plan in firstly make initial npm contribution to jst and after that fix this and other (if any) usability issues in one go for node / npm / bower > Node location should point to the node executable file instead of the parent folder of it > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 04:53:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 22 Oct 2015 04:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120841#comment-13120841 ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- sorry, not following how this relate to this ? > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 05:11:00 2015 From: issues at jboss.org (Thomas Haskes (JIRA)) Date: Thu, 22 Oct 2015 05:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-17859) XML validation error for a web service configuration XML file in a Seam project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120855#comment-13120855 ] Thomas Haskes commented on JBIDE-17859: --------------------------------------- For others that are looking for a solution this may be useful. I had the same problem described above in eclipse, but the solution of adding the aforementioned attributes did not work for me. Adding the attributes made the error disappear, but then my ear would not deploy anymore, stating the error "Unexpected element: handler-chains" while deploying. Adding the following attributes worked though, the error in eclipse disappeard, ant the ear did deploy again: {code:xml} {code} I found that solution here: http://stackoverflow.com/questions/27903735/cannot-find-declaration-of-element-handler-chains-jboss-developer-studio > XML validation error for a web service configuration XML file in a Seam project > ------------------------------------------------------------------------------- > > Key: JBIDE-17859 > URL: https://issues.jboss.org/browse/JBIDE-17859 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Environment: JBDS 8.0.0.Beta3 > Reporter: Ron ?meral > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.CR1 > > > {noformat} > cvc-elt.1: Cannot find the declaration of element 'handler-chains'. > soap-handlers.xml > /seambay-ejb/src/main/resources/org/jboss/seam/example/seambay > line 2 > XML Problem > {noformat} > The file is valid and satisfies the webservices schema in the javaee namespace: http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_services_metadata_handler_2_0.xsd: > {code:xml} > > > > > SOAP Request Handler > org.jboss.seam.webservice.SOAPRequestHandler > > > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 05:59:00 2015 From: issues at jboss.org (Chunyun Chen (JIRA)) Date: Thu, 22 Oct 2015 05:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21009) Can not create openshift application from local template json file In-Reply-To: References: Message-ID: Chunyun Chen created JBIDE-21009: ------------------------------------ Summary: Can not create openshift application from local template json file Key: JBIDE-21009 URL: https://issues.jboss.org/browse/JBIDE-21009 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 OS: Fedora 17 & Windows 8 Reporter: Chunyun Chen Priority: Critical Attachments: local_template.png Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 06:05:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 06:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim reassigned JBIDE-20849: ---------------------------------------- Assignee: Andre Dietisheim > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:19:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120969#comment-13120969 ] Andre Dietisheim commented on JBIDE-20849: ------------------------------------------ What's actually causing this is that there are 2 separate ares for 2 separate links/infos to show up: * singup link * documentation link !connwiz-singup-documentation-areas.png! > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:19:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20849: ------------------------------------- Attachment: connwiz-singup-documentation-areas.png > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:21:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120969#comment-13120969 ] Andre Dietisheim edited comment on JBIDE-20849 at 10/22/15 8:20 AM: -------------------------------------------------------------------- What's actually causing this is that there are 2 separate ares for 2 separate links/infos to show up: * singup link * documentation link OpenShift 3 wont have a signup link since there's no official online site (only OpenShift 2 has it), and OpenShift 2 doesnt have documentations causing either space to get empty. !connwiz-singup-documentation-areas.png! was (Author: adietish): What's actually causing this is that there are 2 separate ares for 2 separate links/infos to show up: * singup link * documentation link !connwiz-singup-documentation-areas.png! > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:21:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120969#comment-13120969 ] Andre Dietisheim edited comment on JBIDE-20849 at 10/22/15 8:20 AM: -------------------------------------------------------------------- What's actually causing this is that there are 2 separate ares for 2 separate links/infos to show up: * singup link * documentation link OpenShift 3 wont have a signup link since there's no official online site (only OpenShift 2 has it), and OpenShift 2 doesnt have documentations causing either space to get empty. !connwiz-singup-documentation-areas.png! was (Author: adietish): What's actually causing this is that there are 2 separate ares for 2 separate links/infos to show up: * singup link * documentation link OpenShift 3 wont have a signup link since there's no official online site (only OpenShift 2 has it), and OpenShift 2 doesnt have documentations causing either space to get empty. !connwiz-singup-documentation-areas.png! > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:32:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 22 Oct 2015 08:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-524) Update SAP tooling to 7.3.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-524. ----------------------------------- Verified with JBDS-IS 8.0.4.CR2 which provides installation of JBoss Fuse SAP Tool Suite 7.3.2.v20151008-1414-H12-CR2. > Update SAP tooling to 7.3.2 > --------------------------- > > Key: JBTIS-524 > URL: https://issues.jboss.org/browse/JBTIS-524 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.4.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.4.CR2 > > > JBDS-IS 8.0.4.CR2 contains Fuse tooling 7.3.2.v20151008-1250-H108-CR2 but SAP tooling is in version 7.3.0.v20150622-1535-H9-Final. > Please create a new build of SAP tooling and add it to https://devstudio.redhat.com/updates/8.0/integration-stack/extras -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:39:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120990#comment-13120990 ] Andre Dietisheim commented on JBIDE-20849: ------------------------------------------ An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:42:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120990#comment-13120990 ] Andre Dietisheim edited comment on JBIDE-20849 at 10/22/15 8:41 AM: -------------------------------------------------------------------- An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. linking to the global howto page seems the best option to me. A gotcha here in every case that the OpenShift 2 howtos are outdated in terms of screenshots at least. The Redhat page with a guide at https://developers.openshift.com/en/getting-started-eclipse.html is severely outdated in text, approach and screenshots. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. was (Author: adietish): An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:42:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 22 Oct 2015 08:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-526) JBDSIS on marketplace contains category for WTP patches In-Reply-To: References: Message-ID: Andrej Podhradsky created JBTIS-526: --------------------------------------- Summary: JBDSIS on marketplace contains category for WTP patches Key: JBTIS-526 URL: https://issues.jboss.org/browse/JBTIS-526 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.3.GA Environment: Eclipse Luna JEE SR2 Reporter: Andrej Podhradsky JBDSIS on marketplace contains category for WTP patches. Is this really intended (see the attached screenshot)? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:42:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120990#comment-13120990 ] Andre Dietisheim edited comment on JBIDE-20849 at 10/22/15 8:41 AM: -------------------------------------------------------------------- An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. linking to the global howto page seems the best option to me. A gotcha here in every case that the OpenShift 2 howtos are outdated in terms of screenshots at least. The Redhat page with a guide at https://developers.openshift.com/en/getting-started-eclipse.html is severely outdated in text, approach and screenshots. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. [~fbricon] thoughts? was (Author: adietish): An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. linking to the global howto page seems the best option to me. A gotcha here in every case that the OpenShift 2 howtos are outdated in terms of screenshots at least. The Redhat page with a guide at https://developers.openshift.com/en/getting-started-eclipse.html is severely outdated in text, approach and screenshots. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:42:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 22 Oct 2015 08:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-526) JBDSIS on marketplace contains category for WTP patches In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-526: ------------------------------------ Attachment: jbdsis803_marketplace_features.png > JBDSIS on marketplace contains category for WTP patches > ------------------------------------------------------- > > Key: JBTIS-526 > URL: https://issues.jboss.org/browse/JBTIS-526 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.3.GA > Environment: Eclipse Luna JEE SR2 > Reporter: Andrej Podhradsky > Attachments: jbdsis803_marketplace_features.png > > > JBDSIS on marketplace contains category for WTP patches. Is this really intended (see the attached screenshot)? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:51:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120990#comment-13120990 ] Andre Dietisheim edited comment on JBIDE-20849 at 10/22/15 8:50 AM: -------------------------------------------------------------------- An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. linking to the global howto page seems the best option to me. A gotcha here in every case that the OpenShift 2 howtos are outdated in terms of screenshots at least. The Redhat page with a guide at https://developers.openshift.com/en/getting-started-eclipse.html is severely outdated in text, approach and screenshots. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. [~fbricon] thoughts? was (Author: adietish): An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. linking to the global howto page seems the best option to me. A gotcha here in every case that the OpenShift 2 howtos are outdated in terms of screenshots at least. The Redhat page with a guide at https://developers.openshift.com/en/getting-started-eclipse.html is severely outdated in text, approach and screenshots. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. [~fbricon] thoughts? > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 08:52:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 08:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120990#comment-13120990 ] Andre Dietisheim edited comment on JBIDE-20849 at 10/22/15 8:51 AM: -------------------------------------------------------------------- An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. Linking to the global howto page seems the best option to me. A gotcha here is in every case that the OpenShift 2 howtos are outdated in terms of screenshots at least. The Redhat page with a guide at https://developers.openshift.com/en/getting-started-eclipse.html is severely outdated in text, approach and screenshots. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. [~fbricon] thoughts? was (Author: adietish): An easy would be to have some documentation for OpenShift 2, but as opposed to OpenShift 3 - which has a page for [all OpenShift3 howtos|http://tools.jboss.org/documentation/howto/openshift3_getting_started.html] - there's no common page for OpenShift2 afaics. Nevertheless we could link to the [Global Howtos Page|http://tools.jboss.org/documentation/howto/], create such a page or link to the [1st howto|http://tools.jboss.org/documentation/howto/openshift_firstapp.html]. On the other this 1st howto wont link to the next one. linking to the global howto page seems the best option to me. A gotcha here in every case that the OpenShift 2 howtos are outdated in terms of screenshots at least. The Redhat page with a guide at https://developers.openshift.com/en/getting-started-eclipse.html is severely outdated in text, approach and screenshots. A more complicated fix would be to present both texts/links in the same text-widget. This wont work for now unfortunately since this requires us to be able to have separate clickable links in the same text, something that's currently prevented by JBIDE-20364. [~fbricon] thoughts? > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 09:33:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21009) Can not create openshift application from local template json file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21009: ------------------------------------- Fix Version/s: 4.3.1.Beta1 > Can not create openshift application from local template json file > ------------------------------------------------------------------ > > Key: JBIDE-21009 > URL: https://issues.jboss.org/browse/JBIDE-21009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 & Windows 8 > Reporter: Chunyun Chen > Priority: Critical > Labels: app, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: local_template.png > > > Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 09:33:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Thu, 22 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21009) Can not create openshift application from local template json file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim reassigned JBIDE-21009: ---------------------------------------- Assignee: Andre Dietisheim > Can not create openshift application from local template json file > ------------------------------------------------------------------ > > Key: JBIDE-21009 > URL: https://issues.jboss.org/browse/JBIDE-21009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 & Windows 8 > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Priority: Critical > Labels: app, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: local_template.png > > > Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 09:36:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 22 Oct 2015 09:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21008) [origin_intservice_49] Can not add/edit service port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill resolved JBIDE-21008. ----------------------------------- Resolution: Duplicate Issue Duplicate of JBIDE-20531 > [origin_intservice_49] Can not add/edit service port > ---------------------------------------------------- > > Key: JBIDE-21008 > URL: https://issues.jboss.org/browse/JBIDE-21008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 > Reporter: Chunyun Chen > Labels: app, openshift_v3 > Attachments: service_port_screenshot.png > > > It can not add/edit service port on "Services & Routing settings" wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 09:45:00 2015 From: issues at jboss.org (Jeff Cantrill (JIRA)) Date: Thu, 22 Oct 2015 09:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21008) [origin_intservice_49] Can not add/edit service port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Cantrill closed JBIDE-21008. --------------------------------- > [origin_intservice_49] Can not add/edit service port > ---------------------------------------------------- > > Key: JBIDE-21008 > URL: https://issues.jboss.org/browse/JBIDE-21008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 > Reporter: Chunyun Chen > Labels: app, openshift_v3 > Attachments: service_port_screenshot.png > > > It can not add/edit service port on "Services & Routing settings" wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 09:50:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 22 Oct 2015 09:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21010) Add validation for a project name in case of duplicates In-Reply-To: References: Message-ID: Fred Bricon created JBIDE-21010: ----------------------------------- Summary: Add validation for a project name in case of duplicates Key: JBIDE-21010 URL: https://issues.jboss.org/browse/JBIDE-21010 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Mari?n Labuda Assignee: Fred Bricon Priority: Optional Fix For: 4.3.1.Beta1 There could be a simple validation of a project name for duplicates. It should not be necessary to hit Finish button in Create OpenShift Project dialog to find out that project already exists based on response from server. Simple validation based on existence of a tree item of project or some similar mechanism would be helpful. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 09:50:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 22 Oct 2015 09:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21010) Add validation for a project name in case of duplicates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-21010: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Add validation for a project name in case of duplicates > ------------------------------------------------------- > > Key: JBIDE-21010 > URL: https://issues.jboss.org/browse/JBIDE-21010 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Fred Bricon > Priority: Optional > Fix For: 4.4.0.Alpha1 > > > There could be a simple validation of a project name for duplicates. It should not be necessary to hit Finish button in Create OpenShift Project dialog to find out that project already exists based on response from server. Simple validation based on existence of a tree item of project or some similar mechanism would be helpful. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 09:51:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 22 Oct 2015 09:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21010) Add validation for a project name in case of duplicates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-21010. --------------------------------- Resolution: Done Fixed in master > Add validation for a project name in case of duplicates > ------------------------------------------------------- > > Key: JBIDE-21010 > URL: https://issues.jboss.org/browse/JBIDE-21010 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Assignee: Fred Bricon > Priority: Optional > Fix For: 4.4.0.Alpha1 > > > There could be a simple validation of a project name for duplicates. It should not be necessary to hit Finish button in Create OpenShift Project dialog to find out that project already exists based on response from server. Simple validation based on existence of a tree item of project or some similar mechanism would be helpful. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:00:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 10:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121049#comment-13121049 ] Nick Boldt commented on JBIDE-21001: ------------------------------------ 546 and 547 make sense, though having the version locked down so tightly in 4.3.x will be good to ensure that builds will fail if someone updates the manifest but forgets to update the EA site. This means there are now FOUR touchpoint places (where previously there were THREE): * root pom (ref to EA URL) * earlyaccess.properties file * manifest.mf * early access .target file But if you actually want jst to depend on angular (not just pretend to) then you need this 4th connection (manifest files), so +1. > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:00:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 10:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121049#comment-13121049 ] Nick Boldt edited comment on JBIDE-21001 at 10/22/15 9:59 AM: -------------------------------------------------------------- 546 and 547 make sense. Having the version locked down tightly in 4.3.x will be good to ensure that builds will fail if someone updates the manifest but forgets to update the EA site. Should we also do that in master? This means there are now FOUR touchpoint places (where previously there were THREE): * root pom (ref to EA URL) * earlyaccess.properties file * manifest.mf * early access .target file But if you actually want jst to depend on angular (not just pretend to) then you need this 4th connection (manifest files), so +1. was (Author: nickboldt): 546 and 547 make sense, though having the version locked down so tightly in 4.3.x will be good to ensure that builds will fail if someone updates the manifest but forgets to update the EA site. This means there are now FOUR touchpoint places (where previously there were THREE): * root pom (ref to EA URL) * earlyaccess.properties file * manifest.mf * early access .target file But if you actually want jst to depend on angular (not just pretend to) then you need this 4th connection (manifest files), so +1. > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 10:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121052#comment-13121052 ] Nick Boldt commented on JBIDE-20976: ------------------------------------ PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >=464 Output: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO/ > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:11:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 10:11:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121063#comment-13121063 ] Nick Boldt commented on JBIDE-20993: ------------------------------------ OK, I've removed the symlinks on devstudio.redhat.com too. Not sure if this will immediately break any staging/release scripts. cc: [~mickael_istria] [~pleacu] > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 10:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20993. ------------------------------ Fix Version/s: 4.3.0.Final (was: 4.3.1.Beta1) Resolution: Done > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:15:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 10:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16158) Investigate tools/processes to templatize CI jobs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-16158: ------------------------------- Summary: Investigate tools/processes to templatize CI jobs (was: Investigate tools/processes to "templatize" CI jobs) > Investigate tools/processes to templatize CI jobs > ------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: devstudio.product_master_diff_generated_vs_server_copy.diff > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:40:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 22 Oct 2015 10:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-399: ------------------------------------ Workaround Description: Need to download target platform for JBDS (contains missing bundles org.eclipse.zest.core and org.eclipse.tm.terminal.ssh) from https://devstudio.jboss.com/static/updates/8.0.0/jboss-devstudio-8.1.0.GA-target-platform.zip was: Need to download target platform for JBDS (contains missing bundles org.eclipse.zest.core and org.eclipse.tm.terminal.ssh) http://devstudio.redhat.com/updates/8.0.0/jbdevstudiotarget-4.41.2.Final.zip http://download.jboss.org/jbosstools/static/targetplatforms/jbdevstudiotarget/4.41.2.Final/jbdevstudiotarget-4.41.2.Final.zip [Obsolete] Download missing dependencies from http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.101/R201408150207/GEF-Update-3.9.101.zip > Cannot install Fuse/SwitchYard tooling in offline mode > ------------------------------------------------------ > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha1 > > Attachments: error.txt, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:58:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 10:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121097#comment-13121097 ] Nick Boldt commented on JBIDE-20976: ------------------------------------ Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_master/ >=4071 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwatch_master/ >=2962 > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 10:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 10:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121099#comment-13121099 ] Alexey Kazakov commented on JBIDE-21001: ---------------------------------------- >> Should we also do that in master? Updated 546. > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 11:28:00 2015 From: issues at jboss.org (Gorkem Ercan (JIRA)) Date: Thu, 22 Oct 2015 11:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gorkem Ercan closed JBIDE-20948. -------------------------------- > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] > ---------------------------------------------------------- > > Key: JBIDE-20948 > URL: https://issues.jboss.org/browse/JBIDE-20948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Aerogear]: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22aerogear-hybrid%22%2C%22cordovasim%22%29] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 11:56:00 2015 From: issues at jboss.org (ecorezgg ecorezgg (JIRA)) Date: Thu, 22 Oct 2015 11:56:00 -0400 (EDT) Subject: [jbosstools-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28JBIDE-21011=29_?= =?utf-8?b?0KTQuNC70YzQvCDQktGA0LDRgtCwINGC0YzQvNGLINGB0LzQvtGC0YDQtdGC?= =?utf-8?b?0Ywg0L7QvdC70LDQudC9INCyINGF0L7RgNC+0YjQtdC8IEhEIDcyMCDQutCw?= =?utf-8?b?0YfQtdGB0YLQstC1INC90LAg0YDRg9GB0YHQutC+0LwgQkRSaXAgMjIuMTAu?= =?utf-8?q?2015?= In-Reply-To: References: Message-ID: ecorezgg ecorezgg created JBIDE-21011: ----------------------------------------- Summary: ????? ????? ???? ???????? ?????? ? ??????? HD 720 ???????? ?? ??????? BDRip 22.10.2015 Key: JBIDE-21011 URL: https://issues.jboss.org/browse/JBIDE-21011 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: ecorezgg ecorezgg ???????? "????? ????" ????? - http://bit.ly/1QSp5pK ???????? "????? ????" ????? - http://bit.ly/1QSp5pK ???????? "????? ????" ????? - http://bit.ly/1QSp5pK --- --- --- ????? ???? ???????? ?????? ? ???????? ???????? hdrip 720 07.10.2015 ???????? ?????? full free movie ????? ????? ???? 2015 07.10.2015 ????? ???? ?????? ??????? ??????? ???????? ?????? ?????????? ?o??a? ???c?? ???????? ?????? 07.10.2015 ????? ???? ???????? ????o 07.10.2015 ????? ???? y?ac? 2015 ???????? ?????? 07.10.2015 ????? ???? ???????? ??????? 07.10.2015 ???????? y?ac? ????? ???? 07.10.2015 ????? ???? ?o????? ???????? 07.10.2015 y??a?? ? ??y??? ???????? 07.10.2015 ????? ???? 2015 ???????? ?????? ???o?o 07.10.2015 ????? ???? ???????? ?????? ?a ?????o?? 07.10.2015 ???o ???????? ?????? ??c??a??o ????? ???? 07.10.2015 ????? ???? ???????? kinogo 07.10.2015 ???????? ??????? ?????a ????? ???? 07.10.2015 ???????? ????? ???? 2 07.10.2015 ???????? ? o?????o? ?a??c??? ????? ???? 07.10.2015 ????? ???? ???????? ?????? ?? 07.10.2015 ???????? ????? ????? ???? ???o?o 07.10.2015 ???????? ????? ???? ????? 07.10.2015 ???????? ????? 2015 ?o?a ????? ???? 07.10.2015 ???????? ????? ????? ???? ?o?????? 07.10.2015 ????? ???? 2015 ???????? ?????? ??????? 07.10.2015 ????? ???? ???????? ?????? ????o 07.10.2015 ???????? ?????? y?ac??? ????? ???? 07.10.2015 ???????? y?ac??? ????? ???? 2015 07.10.2015 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 12:55:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21001: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/544, https://github.com/jbosstools/jbosstools-jst/pull/545, https://github.com/jbosstools/jbosstools-jst/pull/546, https://github.com/jbosstools/jbosstools-jst/pull/547, https://github.com/jbosstools/jbosstools-discovery/pull/316, https://github.com/jbosstools/jbosstools-discovery/pull/315 (was: https://github.com/jbosstools/jbosstools-jst/pull/542, https://github.com/jbosstools/jbosstools-jst/pull/543, https://github.com/jbosstools/jbosstools-jst/pull/546, https://github.com/jbosstools/jbosstools-jst/pull/547, https://github.com/jbosstools/jbosstools-discovery/pull/316, https://github.com/jbosstools/jbosstools-discovery/pull/315) > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L28 > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L11 > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L23-L29 > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 13:01:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 13:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20947. ------------------------------ Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 13:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 13:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121175#comment-13121175 ] Nick Boldt commented on JBIDE-21003: ------------------------------------ Should I pull a new mirror from http://download.eclipse.org/linuxtools/updates-docker-nightly/features/?d or wait for an actual release? Currently, the latest versions of the docker tooling feature are: * http://download.eclipse.org/linuxtools/updates-docker-nightly/features/org.eclipse.linuxtools.docker.feature_1.2.0.201510221601.jar * http://download.eclipse.org/linuxtools/update-neon-docker-m2/features/org.eclipse.linuxtools.docker.feature_1.2.0.201509222207.jar * http://download.eclipse.org/linuxtools/update-mars-1-docker-rc4/features/org.eclipse.linuxtools.docker.feature_1.1.0.201509161915.jar Do we want a different version pulled for 4.3.1.Beta1 / Mars vs. 4.4.0.Alpha1 / Neon? > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 14:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 14:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Attachment: plugins_Mars.0-vs.1.vs.NeonM2.png features_Mars.0-vs.1.vs.NeonM2.png.png After updating TP to M2, we now have a much smaller set of IUs w/ Neon.M2 versions older than Mars.1: {code} org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 org.eclipse.jetty.webapp 9.2.13.v20150730 org.eclipse.jetty.xml 9.2.13.v20150730 org.eclipse.pde.doc.user 3.11.1.v20150903-1352 org.eclipse.platform.doc.user 4.5.1.v20150819-1130 org.eclipse.swt 3.104.1.v20150825-0743 org.eclipse.swt.gtk.linux.x86_64 3.104.1.v20150825-0743 org.eclipse.wst.server.core 1.7.0.v201508271522 org.eclipse.wst.server.discovery 1.1.0.v201508271522 org.eclipse.wst.server.ui 1.5.201.v201509022125 org.eclipse.wst.server_core.feature 3.3.600.v201508271522 org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 {code} -- https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html -- https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html !features_Mars.0-vs.1.vs.NeonM2.png.png! !plugins_Mars.0-vs.1.vs.NeonM2.png! > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 14:15:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 14:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121208#comment-13121208 ] Nick Boldt commented on JBIDE-20993: ------------------------------------ Note that without symlinks we need additional configuration in scripts such as: https://github.com/jbosstools/jbosstools-build-ci/commit/a88ca95a61e3ad7151e26677fc071500407bafda https://github.com/jbosstools/jbosstools-build-ci/commit/07e67973c00ad3fa6c4cffc69bbe8732a48e8583 > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 15:05:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Thu, 22 Oct 2015 15:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121215#comment-13121215 ] Paul Leacu commented on JBTIS-508: ---------------------------------- Added non-version composites to the integration stack snapshots sites for JBT: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/894e2ac9b72a3df1881fd92223f4cb45d994fd33 > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 16:51:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 16:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20991: ----------------------------------- Fix Version/s: 4.3.1.Beta1 > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.Beta1 > > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:10:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20693) Add new features for tools.jboss.org/features/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20693: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Add new features for tools.jboss.org/features/ > ---------------------------------------------- > > Key: JBIDE-20693 > URL: https://issues.jboss.org/browse/JBIDE-20693 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:12:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19282) Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-19282: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) (was: 4.3.1.Beta1) > Unable to add HTML5 Palette tag when JS/CSS references added from JQuery Mobile palette > --------------------------------------------------------------------------------------- > > Key: JBIDE-19282 > URL: https://issues.jboss.org/browse/JBIDE-19282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, MS Windows 7 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Fix For: 4.4.x > > > # Create Hybrid Mobile project > # Add HTML page to www folder with this content > {code:html} > > > {code} > # Insert JS/CSS references from JQuery Mobile palette > # Insert Canvas tag from HTML5 palette inside tag > ERROR: These errors appear in Error log and no tag is added > {noformat} > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.661 > !MESSAGE Program Error: modelStateChanging was less than zero > !STACK 0 > java.lang.IllegalStateException: Program Error: modelStateChanging was less than zero > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.internalModelChanged(AbstractStructuredModel.java:825) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.changedModel(AbstractStructuredModel.java:361) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.changedModel(DOMModelImpl.java:171) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel$DocumentToModelNotifier.noChange(AbstractStructuredModel.java:139) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:513) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1172) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1959) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > !ENTRY org.eclipse.wst.sse.core 4 4 2015-02-17 21:42:06.676 > !MESSAGE Program Error: invalid structured document event > !ENTRY org.eclipse.wst.sse.core 4 2 2015-02-17 21:42:06.676 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.wst.sse.core". > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: assertion failed: > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) > at org.eclipse.jface.text.DocumentEvent.(DocumentEvent.java:62) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1911) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:166) > at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:224) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertIntoEditor(MobilePaletteInsertHelper.java:482) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteItemDropCommand.execute(PaletteItemDropCommand.java:87) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:143) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:127) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:131) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:129) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:115) > at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:98) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398) > at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206) > at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175) > at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140) > at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27) > at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506) > at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179) > at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466) > at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$OtherToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:178) > at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200) > at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574) > at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) > at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) > at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:18:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20986: ----------------------------------- Fix Version/s: 4.3.x 4.4.x (was: 4.3.1.Beta1) Moved to 4.3.x/4.4.x as a not high priority for 4.3.1.Beta1 release > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.x, 4.4.x > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:20:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20943) WP engines are being downloaded but not recognized in UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20943: ----------------------------------- Fix Version/s: 4.3.x 4.4.x (was: 4.3.1.Beta1) > WP engines are being downloaded but not recognized in UI > -------------------------------------------------------- > > Key: JBIDE-20943 > URL: https://issues.jboss.org/browse/JBIDE-20943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.Final > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.x, 4.4.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=479630 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:21:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20320) [FeedHenry] 'Application name:' text field should be greyed out if it is disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20320: ----------------------------------- Fix Version/s: 4.3.x 4.4.x (was: 4.3.1.Beta1) > [FeedHenry] 'Application name:' text field should be greyed out if it is disabled > ----------------------------------------------------------------------------------- > > Key: JBIDE-20320 > URL: https://issues.jboss.org/browse/JBIDE-20320 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.3.x, 4.4.x > > Attachments: Screenshot 2015-07-20 17.55.45.png > > > please see screenshot attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:22:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20768) Display error dialog when no iOS SDKs are found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20768: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > Display error dialog when no iOS SDKs are found > ----------------------------------------------- > > Key: JBIDE-20768 > URL: https://issues.jboss.org/browse/JBIDE-20768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478146 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20768) Display error dialog when no iOS SDKs are found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20768: ----------------------------------- Fix Version/s: 4.4.x > Display error dialog when no iOS SDKs are found > ----------------------------------------------- > > Key: JBIDE-20768 > URL: https://issues.jboss.org/browse/JBIDE-20768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.x, 4.4.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478146 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20694) tools.jboss.org/features: Add FeedHenry In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20694: ----------------------------------- Fix Version/s: 4.3.x 4.4.x (was: 4.3.1.Beta1) > tools.jboss.org/features: Add FeedHenry > --------------------------------------- > > Key: JBIDE-20694 > URL: https://issues.jboss.org/browse/JBIDE-20694 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Alexey Kazakov > Assignee: Gorkem Ercan > Fix For: 4.3.x, 4.4.x > > > We should add FeedHanry to tools.jboss.org/features > Probably to Aeroger/mobile development tooling? Or create a new page there? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:24:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20693) Add new features for tools.jboss.org/features/ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20693. ------------------------------------ Fix Version/s: 4.3.0.Final (was: 4.3.1.Final) Resolution: Done > Add new features for tools.jboss.org/features/ > ---------------------------------------------- > > Key: JBIDE-20693 > URL: https://issues.jboss.org/browse/JBIDE-20693 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20912) Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20912: ----------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.Beta1) > Enable / Disable LiveReload settings have no effect for pages with already injected LiveReload.js > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.4.x > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:57:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20757) Livereload does not work with CordovaSim on default THYM project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20757: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Livereload does not work with CordovaSim on default THYM project > ---------------------------------------------------------------- > > Key: JBIDE-20757 > URL: https://issues.jboss.org/browse/JBIDE-20757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, cordovasim, livereload, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > Steps to reproduce: > 1) create default THYM project > 2) enable Livereload server > 3) run THYM project on CordovaSim > 4) edit index.html and save changes > ERROR: refresh is not happening on Cordovasim > In order to make it work one nee to remove the following meta tag from index.html: > {code} > > {code} > Livereload doesn't work with new THYM projects due to new cordova-white-list plugin security policy - https://github.com/apache/cordova-plugin-whitelist/blob/master/README.md#content-security-policy . The following error prevent script loading > {code} > Refused to load the script 'http://localhost:35729/livereload.js' because it violates the following Content Security Policy directive: "default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'". Note that 'script-src' was not explicitly set, so 'default-src' is used as a fallback. > {code} > BTW, We are not the only one affected by this changes - http://forum.ionicframework.com/t/solution-for-livereload-problems-with-new-csp-rules/25449 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 17:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 17:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20745) Livereload doesn't work stable with CordovaSim / BrowserSim In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20745: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Livereload doesn't work stable with CordovaSim / BrowserSim > ----------------------------------------------------------- > > Key: JBIDE-20745 > URL: https://issues.jboss.org/browse/JBIDE-20745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim, livereload > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.1.Final > > > It seems that Livereload stopped working on simple pages like: > {code} > > > > Insert title here > > >

Hello World

> > > {code} > But at the same time it works fine with some complex projects like jboss-as-kitchensink-html5-mobile & https://github.com/ibuziuk/cordovasim-demo -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20771) Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20771: ----------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.Beta1) > Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20771 > URL: https://issues.jboss.org/browse/JBIDE-20771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.x > > Attachments: csp.png > > > This problem might be treated as an edge case from the first glance, but actually it might have a sufficient impact on Livereload in the short run. *CSP* is sort of security policy which complements *CORS*. However, Content Security Policy and CORS are two separate things. CORS is the web service declaring which apps are authorized to call the service. > Content Security Policy is kind of the opposite: it's the app that declares which services can be called. > Basically, [Content Security Policy|http://www.html5rocks.com/en/tutorials/security/content-security-policy/] is supported by new versions on major browsers in order to prevent Cross-site scripting (XSS) attacks. However, this policy restricts the usage of LiveReload to the certain extend. > Steps to reproduce: > 1) Create default *jboss-as-kitchensink-html5-mobile* > 2) Add CSP meta tag > {code} > > {code} > ^ allow to use jquery (other stuff is hosted locally) > 3) In Preferences (General -> Web Browser) add newest version of chrome and set as default > 4) Run the project on the Local Server (Tomcat) > 5) In the Server View right-click on the hosted project -> Show In -> Web Browser via LiveReload > 6) Edit and save index.html > 7) ERROR: Livereload is broken - CSP has prevented *livereload.js* injection > !csp.png! > N.B. LiveReload will work with the file protocol (right click on index.html -> *Open With* -> *Web Browser with LiveReload*) even with CSP enabled, cause in this case livereload.js is hosted on the same port (35729 by default) as the whole project > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:04:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20771) Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121261#comment-13121261 ] Alexey Kazakov commented on JBIDE-20771: ---------------------------------------- There is not much we can do actually. Or you have some ideas? Moving to 4.4.x. > Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20771 > URL: https://issues.jboss.org/browse/JBIDE-20771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.x > > Attachments: csp.png > > > This problem might be treated as an edge case from the first glance, but actually it might have a sufficient impact on Livereload in the short run. *CSP* is sort of security policy which complements *CORS*. However, Content Security Policy and CORS are two separate things. CORS is the web service declaring which apps are authorized to call the service. > Content Security Policy is kind of the opposite: it's the app that declares which services can be called. > Basically, [Content Security Policy|http://www.html5rocks.com/en/tutorials/security/content-security-policy/] is supported by new versions on major browsers in order to prevent Cross-site scripting (XSS) attacks. However, this policy restricts the usage of LiveReload to the certain extend. > Steps to reproduce: > 1) Create default *jboss-as-kitchensink-html5-mobile* > 2) Add CSP meta tag > {code} > > {code} > ^ allow to use jquery (other stuff is hosted locally) > 3) In Preferences (General -> Web Browser) add newest version of chrome and set as default > 4) Run the project on the Local Server (Tomcat) > 5) In the Server View right-click on the hosted project -> Show In -> Web Browser via LiveReload > 6) Edit and save index.html > 7) ERROR: Livereload is broken - CSP has prevented *livereload.js* injection > !csp.png! > N.B. LiveReload will work with the file protocol (right click on index.html -> *Open With* -> *Web Browser with LiveReload*) even with CSP enabled, cause in this case livereload.js is hosted on the same port (35729 by default) as the whole project > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:05:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20924) Write a blog about the changes in the Eclipse Hibernate tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-20924. ---------------------------------- > Write a blog about the changes in the Eclipse Hibernate tooling > --------------------------------------------------------------- > > Key: JBIDE-20924 > URL: https://issues.jboss.org/browse/JBIDE-20924 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.1.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:11:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20743) HTML file is not properly rendered after saving and reopening In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20743: ----------------------------------- Fix Version/s: 4.3.x 4.4.x (was: 4.4.0.Alpha1) (was: 4.3.1.Beta1) > HTML file is not properly rendered after saving and reopening > ------------------------------------------------------------- > > Key: JBIDE-20743 > URL: https://issues.jboss.org/browse/JBIDE-20743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150918-0257-B105 Fedora 22 64 bit KDE HTML support for VPE enabled > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.3.x, 4.4.x > > > See this comment https://issues.jboss.org/browse/JBIDE-20611?focusedCommentId=13110704&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110704 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:18:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 18:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121264#comment-13121264 ] Nick Boldt commented on JBIDE-20992: ------------------------------------ Found a workaround: use `-Dmaven.deploy.skip=true` when building in Jenkins to skip the nexus deployment. Does not skip the deploy-to-jboss.org profile, which puts bits here: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-freemarker_4.3.mars/ I think we should do this for all the JBT projects, since NONE of the projects' contents in Nexus is actually used downstream -- only Locus & Browsersim Standalone bits are published that way. [~akazakov] [~maxandersen] [~dgolovin] [~mickael_istria] WDYT? --- That said I think I found the reason why this one project won't deploy correctly. https://github.com/jbosstools/jbosstools-freemarker/commit/b4c28ff7b02ec24a127b56d06ed3c7b03472c6f4 So we could fix JBIDE-20908 and this project should again be able to deploy to nexus. But as I ask above... why do we want that? We could enable maven.deploy.skip=true in the parent pom for all the projects (except Locus and Browsersim Standalone). > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:34:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20746) ds_my_next_maint_unresolved needs updating to 4.3.1.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121266#comment-13121266 ] Alexey Kazakov commented on JBIDE-20746: ---------------------------------------- next_maint looks correct now -> "pattern": "4.3.(?!x).*" But the filter still shows 4.3.0.CR2 only issues and doesn't show 4.3.1.Beta1 issues. Any idea why? > ds_my_next_maint_unresolved needs updating to 4.3.1.Final > --------------------------------------------------------- > > Key: JBIDE-20746 > URL: https://issues.jboss.org/browse/JBIDE-20746 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.3.1.Beta1 > > > My ds_my_next_maint_unresolved is currently empty despite having jiras targeted to 4.3.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:38:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-18820: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.x > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:41:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19846) Remove generated files after user decides to delete imported unuseful root In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-19846: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > Remove generated files after user decides to delete imported unuseful root > -------------------------------------------------------------------------- > > Key: JBIDE-19846 > URL: https://issues.jboss.org/browse/JBIDE-19846 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.x > > > When user selects folder root that contains no real data (e.g. workspace root) importer asks if he wants to delete the project after import. However, even if the project is deleted from workspace, the generated files (e.g .settings, .project) still remain on the filesystem. These should be deleted as they are clearly not needed nor desired. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:42:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20765: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.x > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:43:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20765: ----------------------------------- Component/s: central > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, discovery > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:43:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20765: ----------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, discovery > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19765) Add description to easy import wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-19765: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Add description to easy import wizard > ------------------------------------- > > Key: JBIDE-19765 > URL: https://issues.jboss.org/browse/JBIDE-19765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: wizard.png > > > There is no descrption of the wizard (see picture attached). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 18:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 18:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-19768: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Add possibility to select which nested projects to import > --------------------------------------------------------- > > Key: JBIDE-19768 > URL: https://issues.jboss.org/browse/JBIDE-19768 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import. > Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 19:16:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 19:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20737: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > On Linux, non-root user us not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 19:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 22 Oct 2015 19:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-20737: -------------------------------------- Assignee: Xavier Coulon (was: Misha Ali) The blog and documentation have been updated. Assigning to [~xcoulon] to see what else we can do. > On Linux, non-root user us not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 21:39:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 21:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121280#comment-13121280 ] Nick Boldt commented on JBIDE-18820: ------------------------------------ [~akazakov] Could we just close this and open a new issue if there's further devdoc needed? > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.x > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 21:39:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Thu, 22 Oct 2015 21:39:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121280#comment-13121280 ] Nick Boldt edited comment on JBIDE-18820 at 10/22/15 9:38 PM: -------------------------------------------------------------- [~akazakov] Could we just close this and open a new issue if there's further devdoc needed? Figure if after 2 weeks there's been no feedback on my work, it must be good... right? :D was (Author: nickboldt): [~akazakov] Could we just close this and open a new issue if there's further devdoc needed? > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.x > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 03:05:01 2015 From: issues at jboss.org (Xavier Coulon (JIRA)) Date: Fri, 23 Oct 2015 03:05:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121296#comment-13121296 ] Xavier Coulon commented on JBIDE-20737: --------------------------------------- For the record, this article might help: http://www.projectatomic.io/blog/2015/08/why-we-dont-let-non-root-users-run-docker-in-centos-fedora-or-rhel/ > On Linux, non-root user us not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 03:48:00 2015 From: issues at jboss.org (David Hladky (JIRA)) Date: Fri, 23 Oct 2015 03:48:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121313#comment-13121313 ] David Hladky commented on JBDS-3547: ------------------------------------ If you click on the [http://tools.jboss.org/downloads/devstudio/mars/9.0.0.GA.html|http://tools.jboss.org/downloads/devstudio/mars/9.0.0.GA.html] link and hower above the download links (any version), all the link start with the Eloqua server [http://www.redhat.com/j/elqNow/elqRedir.htm?ref=....] and the reference goes to the Download manager. The correct version should be just the Download manager link (the four dots from my example). > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 06:50:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 06:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121394#comment-13121394 ] Max Rydahl Andersen commented on JBIDE-18820: --------------------------------------------- its assigned to me - i'll close it when I can. > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.x > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 06:54:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 06:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121398#comment-13121398 ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- ok, but that makes perfect sense to have since otherwise these scripts are version/distribution specific anyway. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 07:15:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 07:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121411#comment-13121411 ] Max Rydahl Andersen commented on JBIDE-20992: --------------------------------------------- Please open separate issue if you want to suggest stopping publish to nexus. Lets this be about fixing the actual error since it probably hides some issue either in our build or in nexus. All the links I tried to follow above gave 404 so I guess the build have been deleted. Can you provide info on what the actual error reported was ? > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 07:17:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 07:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121413#comment-13121413 ] Max Rydahl Andersen commented on JBIDE-20992: --------------------------------------------- I don't grok what part of https://github.com/jbosstools/jbosstools-freemarker/commit/b4c28ff7b02ec24a127b56d06ed3c7b03472c6f4 should be the cause ? as long as we changed it back to have .qualifier/snapshot after this was released it should be fine. Could you be more specific ? > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 07:18:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 07:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121415#comment-13121415 ] Max Rydahl Andersen commented on JBIDE-20992: --------------------------------------------- ah, I just saw that https://issues.jboss.org/browse/JBIDE-20908 was fixed and explain why I don't see the issue in the code anymore. So this issue can be fixed and resolved ? > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 07:58:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 07:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBDS-3549: ----------------------------------------- Summary: Developer - start and stop the CDK easily from within the IDE Key: JBDS-3549 URL: https://issues.jboss.org/browse/JBDS-3549 Project: Developer Studio (JBoss Developer Studio) Issue Type: Story Reporter: Max Rydahl Andersen User Story: As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. Acceptance Criteria: * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse * If CDK is running, clicking stop should halt the CDK and docker * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 07:58:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 07:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBDS-3551: ----------------------------------------- Summary: JavaEE Developer - be able to start/stop applications on docker with debug on/off Key: JBDS-3551 URL: https://issues.jboss.org/browse/JBDS-3551 Project: Developer Studio (JBoss Developer Studio) Issue Type: Story Reporter: Max Rydahl Andersen User Story: As a JavaEE Developer I should be able to start/stop applications with debug turned on or off Acceptance Criteria: * Developer can start/stop an application from a central place, no CLI operations needed. * Developer can start with or without debug enabled * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 07:58:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 07:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBDS-3552: ----------------------------------------- Summary: Developer - be able to incrementally deploy changes to docker containers Key: JBDS-3552 URL: https://issues.jboss.org/browse/JBDS-3552 Project: Developer Studio (JBoss Developer Studio) Issue Type: Story Reporter: Max Rydahl Andersen User Story: As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. Acceptance Criteria: * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 07:58:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 07:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBDS-3550: ----------------------------------------- Summary: Developer - autodetect the CDK in IDE Key: JBDS-3550 URL: https://issues.jboss.org/browse/JBDS-3550 Project: Developer Studio (JBoss Developer Studio) Issue Type: Story Reporter: Max Rydahl Andersen User Story: As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use Acceptance Criteria: * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 08:23:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Fri, 23 Oct 2015 08:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121456#comment-13121456 ] Supriya Bharadwaj commented on TOOLSDOC-307: -------------------------------------------- > Chaecked where can the info be added in the existing artilces for OS2 > Decided on > https://access.redhat.com/articles/1295883#republishmodifiedapp > Add a note or another sentence in the task (and not in the DYK section since the info will be easily spotted in the task) > Tried the same steps on OS3 to confirm if the addition must be made in OS3 docs too > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 08:38:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 08:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Rydahl Andersen updated JBDS-3549: -------------------------------------- Fix Version/s: 9.1.0.Beta1 > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Reporter: Max Rydahl Andersen > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 08:41:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 08:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20737) On Linux, non-root user is not able to use auto-detect to access running Docker instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20737: -------------------------------- Summary: On Linux, non-root user is not able to use auto-detect to access running Docker instance (was: On Linux, non-root user us not able to use auto-detect to access running Docker instance ) > On Linux, non-root user is not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 08:45:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 08:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3534) Provide UI to see/export Central configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121471#comment-13121471 ] Fred Bricon commented on JBDS-3534: ----------------------------------- In about Eclipse > installation details > configuration, you can see what parameters are by central: {noformat}org.jboss.tools.resolved.remote.properties=examples.categories.url|jbosstools|4.3=http://download.jboss.org/jbosstools/examples/4.3/project-examples-category-4.3.xml ======= jboss.central.webpage.url=https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=public-jboss&g=org.jboss.tools.central&a=jbosstools-central-webpage&v=0.0.1-SNAPSHOT&e=zip&mustEndWith=.zip maven.examples.url|jbosstools|4.3=http://download.jboss.org/jbosstools/examples/4.3/project-examples-maven-4.3.0.Beta2.xml jboss.discovery.site.url|jbosstools|4.3=http://download.jboss.org/jbosstools/mars/stable/updates/ jboss.discovery.directory.url|jbosstools|4.3=http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml jboss.discovery.earlyaccess.site.url|jbosstools|4.3=http://download.jboss.org/jbosstools/mars/stable/updates/earlyaccess/ jboss.discovery.site.integration-stack.url|jbosstools|4.3=http://download.jboss.org/jbosstools/mars/stable/updates/integration-stack/discovery/ openshift.userdoc.url=http://tools.jboss.org/documentation/howto/openshift3_getting_started.html jboss.discovery.site.integration-stack-sap.url|jbosstools|4.3=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/extras/ buzz.feed.url=http://planet.jboss.org/feeds/buzz jboss.discovery.earlyaccess.list.url|jbosstools|4.3=http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-earlyaccess.properties quickstarts.search.query=http://dcp.jboss.org/v1/rest/search?content_provider=jboss-developer&content_provider=rht&field=target_product&field=github_repo_url&field=sys_description&field=sys_title&field=sys_tags&field=sys_type&field=experimental&field=git_download&field=prerequisites&field=quickstart_id&field=git_tag&field=git_commit&query=sys_type:(quickstart)&size=500 community.examples.url|jbosstools|4.3=http://download.jboss.org/jbosstools/examples/4.3/project-examples-community-4.3.0.Beta2.xml jboss.discovery.site.integration-stack-sap.feature=org.fusesource.ide.sap.feature.feature.group featured.examples.url|jbosstools|4.3=http://download.jboss.org/jbosstools/examples/4.3/project-examples-shared-4.3.0.Beta2.xml jboss.discovery.earlyaccess.site.integration-stack.url|jbosstools|4.3=http://download.jboss.org/jbosstools/mars/stable/updates/integration-stack/discovery/earlyaccess/ portal.examples.url|jbosstools|4.3=http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-examples-jboss-portal6.2-jbds8.0-001.xml {noformat} > Provide UI to see/export Central configuration > ---------------------------------------------- > > Key: JBDS-3534 > URL: https://issues.jboss.org/browse/JBDS-3534 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > Affects Versions: 8.0.2.GA, 8.1.0.GA, 9.0.0.GA > Reporter: Denis Golovin > Fix For: LATER > > > In current and previous releases it is not possible to investigate issues reported against Central, because of configuration complexity which involves to many local and remote resources. Would be good to have some sort of UI that would let to see what is actually used in central to fill Software/Update tab. This way in case of issues like this JBDS-3533 we at least would have a way to see what is actually used on client side. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 08:45:01 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 08:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3534) Provide UI to see/export Central configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBDS-3534: ------------------------------ Fix Version/s: LATER > Provide UI to see/export Central configuration > ---------------------------------------------- > > Key: JBDS-3534 > URL: https://issues.jboss.org/browse/JBDS-3534 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > Affects Versions: 8.0.2.GA, 8.1.0.GA, 9.0.0.GA > Reporter: Denis Golovin > Fix For: LATER > > > In current and previous releases it is not possible to investigate issues reported against Central, because of configuration complexity which involves to many local and remote resources. Would be good to have some sort of UI that would let to see what is actually used in central to fill Software/Update tab. This way in case of issues like this JBDS-3533 we at least would have a way to see what is actually used on client side. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-21012: ---------------------------------- Summary: Why do we deploy JBT components to Nexus snapshots repo? Key: JBIDE-21012 URL: https://issues.jboss.org/browse/JBIDE-21012 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 Reporter: Nick Boldt Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: * eat disk space in Nexus * consume time/resources in Jenkins Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:10:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:10:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121521#comment-13121521 ] Nick Boldt commented on JBIDE-20992: ------------------------------------ The actual error was reported in the linked log file: {code}org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project freemarker.site: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.freemarker:freemarker.site:zip:1.5.1 from/to jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/): Failed to transfer file: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/org/jboss/tools/freemarker/freemarker.site/1.5.1/freemarker.site-1.5.1.zip. Return code is: 401, ReasonPhrase: Unauthorized.{code} I've opened JBIDE-21012 to discuss not deploying snapshots to nexus at all. Since JBIDE-20908 is fixed again, we can now close this. > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:10:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:10:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt closed JBIDE-20992. ------------------------------ Assignee: Nick Boldt (was: Mickael Istria) Resolution: Done I reverted the changes I did to the freemarker job and it is once again blue on the dev180-rhel6-x86_64 slave. Closing. > Why is freemarker build failing to deploy to nexus? > --------------------------------------------------- > > Key: JBIDE-20992 > URL: https://issues.jboss.org/browse/JBIDE-20992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, freemarker > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: deployment.fail.txt > > > Freemarker build is failing to deploy the site to nexus. > Log snippet: [^deployment.fail.txt], taken from > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 ) > vs. > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 ) > * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) > Far as I can tell (?) there's: > * no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), > * no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1]) > * no significant difference when comparing root poms [2], [3] > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/ > [2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64 > Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted: > [4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36 > -- > Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5]. > [5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120 > Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`. > So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ? > -- > (Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21012: ------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21012: ---------------------------------- Assignee: Nick Boldt > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:30:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121547#comment-13121547 ] Nick Boldt commented on JBIDE-20993: ------------------------------------ Yes: you're making my code better by forcing me to remove the shortcuts. :D > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:34:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Fri, 23 Oct 2015 10:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3547: ----------------------------- > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:34:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3547: ----------------------------- Status: New (was: New) Target Release: 9.1.0.GA > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:35:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:35:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3547: ----------------------------- Status: New (was: New) > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:35:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:35:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3547: ----------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-website/pull/524/files Pull request to approve: https://github.com/jbosstools/jbosstools-website/pull/524/files > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBDS-3547: -------------------------------- Assignee: Alexey Kazakov > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:37:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:37:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3547: ----------------------------- Fix Version/s: 8.1.1.GA 9.0.0.GA 8.1.0.GA 8.0.0.GA 7.1.1.GA > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:37:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 10:37:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3547: ----------------------------- Fix Version/s: 9.1.0.Beta1 > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 10:59:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 10:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20946) Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20946: ------------------------------------- Fix Version/s: 4.3.1.Beta1 > Add multi-tag filtering to templates > ------------------------------------ > > Key: JBIDE-20946 > URL: https://issues.jboss.org/browse/JBIDE-20946 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Priority: Optional > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:00:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 11:00:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121581#comment-13121581 ] Alexey Kazakov commented on JBDS-3547: -------------------------------------- Is it some recent change or it was always wrong to use the Eloqua server in the links in tools.jboss.org/downloads? > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:00:02 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 11:00:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20946) Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121584#comment-13121584 ] Andre Dietisheim commented on JBIDE-20946: ------------------------------------------ [~fbricon] looks like we need this to select a template for the "new-app" functionality that we strive for. Setting 4.3.0.Beta1 as fixVersion > Add multi-tag filtering to templates > ------------------------------------ > > Key: JBIDE-20946 > URL: https://issues.jboss.org/browse/JBIDE-20946 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Priority: Optional > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:01:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 11:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20946) New Application wizard: Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20946: ------------------------------------- Summary: New Application wizard: Add multi-tag filtering to templates (was: Add multi-tag filtering to templates) > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-20946 > URL: https://issues.jboss.org/browse/JBIDE-20946 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:01:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 11:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20946) New Application wizard: Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-20946: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-20946 > URL: https://issues.jboss.org/browse/JBIDE-20946 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:13:00 2015 From: issues at jboss.org (=?UTF-8?Q?Miroslav_Za=C5=A5ko_=28JIRA=29?=) Date: Fri, 23 Oct 2015 11:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121593#comment-13121593 ] Miroslav Za?ko commented on JBIDE-16503: ---------------------------------------- Issue still appears in Eclipse Mars Release (4.5.0) Build id: 20150621-1200 & Hibernate tools 5.0.0.Final-v20150924022210B39 > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.0.Beta2 > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:16:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 11:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-16503: ----------------------------------- Fix Version/s: 4.3.x (was: 4.2.0.Beta2) > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x, 4.4.x > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:16:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 11:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-16503: ----------------------------------- Fix Version/s: 4.4.x > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x, 4.4.x > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:16:01 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 11:16:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121595#comment-13121595 ] Alexey Kazakov commented on JBIDE-16503: ---------------------------------------- [~koen.aers] please take a look. > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x, 4.4.x > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:33:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 11:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121611#comment-13121611 ] Nick Boldt commented on JBTIS-508: ---------------------------------- Looks good but for one thing: if you remove the quality qualifier in the site name, you will have one less thing to change when moving from CI -> staging -> development -> stable. See my direct email for fleshed out details / examples. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:37:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 11:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121613#comment-13121613 ] Fred Bricon commented on JBDS-3489: ----------------------------------- Mockup of modified UI to add workspace project selection: !project-selection.png! Selecting a workspace project would trigger a number of things: - check if the project is shared with git. If not, display error message, enable the share with git link that'd open the egit wizard - the type of project would be determined, which, if 'Matching template's is enabled, would filter the templates of the selected openshift project per matching tags - default selected templates could be determined by a list of hard coded template names (eg. eap6-basic-s2i, else eap6-basic-sti for EAP) - remote git repo url and git context dir would be determined. Matching values would be injected to known template parameters (git_uri/source_repository_url, git_context_dir/context_dir), if they're present in the selected template, > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.0.1.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:40:02 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 11:40:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121613#comment-13121613 ] Fred Bricon edited comment on JBDS-3489 at 10/23/15 11:39 AM: -------------------------------------------------------------- Mockup of modified UI to add workspace project selection: !project-selection.png! Selecting a workspace project would trigger a number of things: - check if the project is shared with git. If not, display error message, enable the share with git link that'd open the egit wizard - the type of project would be determined, which, if 'Matching template's is enabled, would filter the templates of the selected openshift project per matching tags - default selected templates could be determined by a list of hard coded template names (eg. eap6-basic-s2i, else eap6-basic-sti for EAP) - remote git repo url and git context dir would be determined. Matching values would be injected to known template parameters (git_uri/source_repository_url, git_context_dir/context_dir), if they're present in the selected template At the end of the application creation process, the git import wizard would NOT be called, because the project already exists in the workspace. was (Author: fbricon): Mockup of modified UI to add workspace project selection: !project-selection.png! Selecting a workspace project would trigger a number of things: - check if the project is shared with git. If not, display error message, enable the share with git link that'd open the egit wizard - the type of project would be determined, which, if 'Matching template's is enabled, would filter the templates of the selected openshift project per matching tags - default selected templates could be determined by a list of hard coded template names (eg. eap6-basic-s2i, else eap6-basic-sti for EAP) - remote git repo url and git context dir would be determined. Matching values would be injected to known template parameters (git_uri/source_repository_url, git_context_dir/context_dir), if they're present in the selected template, > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.0.1.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:43:00 2015 From: issues at jboss.org (=?UTF-8?Q?Miroslav_Za=C5=A5ko_=28JIRA=29?=) Date: Fri, 23 Oct 2015 11:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121593#comment-13121593 ] Miroslav Za?ko edited comment on JBIDE-16503 at 10/23/15 11:42 AM: ------------------------------------------------------------------- Issue still appears in Eclipse Mars Release (4.5.0) Build id: 20150621-1200 & Hibernate tools 5.0.0.Final-v20150924022210B39 {{export SWT_GTK3=0}} is still a workaround was (Author: mirec.zatko): Issue still appears in Eclipse Mars Release (4.5.0) Build id: 20150621-1200 & Hibernate tools 5.0.0.Final-v20150924022210B39 > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x, 4.4.x > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:45:01 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Fri, 23 Oct 2015 11:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121620#comment-13121620 ] Denis Golovin commented on JBDS-3276: ------------------------------------- First screenshot is a bug, easy to fix. I just copied runtime detection table and didn't notice that column name. It was and is just a prototype, so we can understand what kind of issues we might have with selected approach to build JBDSIS installer. Second is not easy to fix in a good manner because it seems p2 has no means to calculate the size of features selected for installation. I'll dig in p2 query spec again and see if we I can access size property for IU. If it is possible then there is a chance to fix that property and show actual size after installation close to reality. Otherwise we should just add approximate size in additional features metadata in .json file and just addb it to initial JBDS size. > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:58:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 11:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-16503: ----------------------------------- Component/s: upstream > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x, 4.4.x > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 11:59:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 11:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-16503: -------------------------------------- Assignee: Snjezana Peco (was: Koen Aers) Assigning to [~snjeza] since this is a SWT GTK3 issue. > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Snjezana Peco > Fix For: 4.3.x, 4.4.x > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 12:44:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 12:44:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp In-Reply-To: References: Message-ID: Nick Boldt created JBTIS-527: -------------------------------- Summary: com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp Key: JBTIS-527 URL: https://issues.jboss.org/browse/JBTIS-527 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 9.0.0.Alpha2 Reporter: Nick Boldt Priority: Blocker Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.Alpha2.jbds-is/earlyaccess/ I see these 4 IUs: {code} com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 {code} They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: * 9.0.0.Alpha2-v20151006-2058-B148 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 12:55:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21009) Can not create openshift application from local template json file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121666#comment-13121666 ] Andre Dietisheim commented on JBIDE-21009: ------------------------------------------ merged and pushed to upstream/jbosstools-4.3.x > Can not create openshift application from local template json file > ------------------------------------------------------------------ > > Key: JBIDE-21009 > URL: https://issues.jboss.org/browse/JBIDE-21009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 & Windows 8 > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Priority: Critical > Labels: app, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: local_template.png > > > Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 12:55:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21013) Can not create openshift application from local template json file In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-21013: ---------------------------------------- Summary: Can not create openshift application from local template json file Key: JBIDE-21013 URL: https://issues.jboss.org/browse/JBIDE-21013 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 OS: Fedora 17 & Windows 8 Reporter: Chunyun Chen Assignee: Andre Dietisheim Priority: Critical Fix For: 4.3.1.Beta1 Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 12:55:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21013) Can not create openshift application from local template json file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21013: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Can not create openshift application from local template json file > ------------------------------------------------------------------ > > Key: JBIDE-21013 > URL: https://issues.jboss.org/browse/JBIDE-21013 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 & Windows 8 > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Priority: Critical > Labels: app, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: local_template.png > > > Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 12:57:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 12:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20946) New Application wizard: Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20946: ----------------------------------- Assignee: Fred Bricon > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-20946 > URL: https://issues.jboss.org/browse/JBIDE-20946 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 13:08:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 13:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-19536: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > Infinite job loop when creating project > --------------------------------------- > > Key: JBIDE-19536 > URL: https://issues.jboss.org/browse/JBIDE-19536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump, workspace_jbds9_endless_building_loop.rar > > > Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974 > I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 13:10:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 13:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18497) Importing PicketLink quickstart raises error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-18497: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) The upstream issue is fixed in upcoming Mars.2 > Importing PicketLink quickstart raises error > -------------------------------------------- > > Key: JBIDE-18497 > URL: https://issues.jboss.org/browse/JBIDE-18497 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1 > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Labels: upstream, xml_validation_quickstarts_redirect > Fix For: 4.3.1.Final > > > Steps to recreate issue: > * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap > * Install JBDS8.0.CR1 > * Import-> Existing Maven Projects - select the quickstart > The error is: > jboss-picketlink-sts > Referenced file contains errors (http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-wsse-server.xml /jboss-picketlink-sts/src/main/webapp/WEB-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 13:19:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 13:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20711) Changing deploy-name in component xml file will not take effect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121672#comment-13121672 ] Alexey Kazakov commented on JBIDE-20711: ---------------------------------------- This would require a new API, so it's not double for Mars.2? Anyway I'm moving it out of 4.3.1.Beta1 because of low priority comparing to other deployment task we have for that time frame. > Changing deploy-name in component xml file will not take effect > --------------------------------------------------------------- > > Key: JBIDE-20711 > URL: https://issues.jboss.org/browse/JBIDE-20711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.x > > > Steps to replicate: > 1) Create a dynamic web project TestProject > 2) Create a server > 3) Add/Remove action in servers view. You will see the module name is TestProject > 4) Open the component.xml file in .settings folder and change deploy-name to some new value (RobsTest) > 5) Add/Remove, note module name didn't change > 6) Publish deployment, note its still deploying as TestProject > 7) Close project, then re-open it > 8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar) > 9) Publish, note module is deployed as RobsTest.war -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 13:19:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 13:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20711) Changing deploy-name in component xml file will not take effect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20711: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > Changing deploy-name in component xml file will not take effect > --------------------------------------------------------------- > > Key: JBIDE-20711 > URL: https://issues.jboss.org/browse/JBIDE-20711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.x > > > Steps to replicate: > 1) Create a dynamic web project TestProject > 2) Create a server > 3) Add/Remove action in servers view. You will see the module name is TestProject > 4) Open the component.xml file in .settings folder and change deploy-name to some new value (RobsTest) > 5) Add/Remove, note module name didn't change > 6) Publish deployment, note its still deploying as TestProject > 7) Close project, then re-open it > 8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar) > 9) Publish, note module is deployed as RobsTest.war -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 13:53:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 13:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21013) Can not create openshift application from local template json file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121680#comment-13121680 ] Andre Dietisheim commented on JBIDE-21013: ------------------------------------------ merged and pushed to upstream/master > Can not create openshift application from local template json file > ------------------------------------------------------------------ > > Key: JBIDE-21013 > URL: https://issues.jboss.org/browse/JBIDE-21013 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 & Windows 8 > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Priority: Critical > Labels: app, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: local_template.png > > > Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 14:17:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21014) Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-21014: ---------------------------------- Summary: Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins Key: JBIDE-21014 URL: https://issues.jboss.org/browse/JBIDE-21014 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html-source-editing, updatesite, upstream Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 Reporter: Nick Boldt org.jboss.tools.jst.angularjs.test 3.7.1.qualifier will soon require org.eclipse.angularjs.jsp.core [1.0.0] but it's not (yet) in the AngularJS mirror. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 14:17:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21014) Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21014: ------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins > ---------------------------------------------------------------------------- > > Key: JBIDE-21014 > URL: https://issues.jboss.org/browse/JBIDE-21014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, updatesite, upstream > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > org.jboss.tools.jst.angularjs.test 3.7.1.qualifier will soon require org.eclipse.angularjs.jsp.core [1.0.0] but it's not (yet) in the AngularJS mirror. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 14:17:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 14:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21014) Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21014: ---------------------------------- Assignee: Nick Boldt > Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins > ---------------------------------------------------------------------------- > > Key: JBIDE-21014 > URL: https://issues.jboss.org/browse/JBIDE-21014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, updatesite, upstream > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > org.jboss.tools.jst.angularjs.test 3.7.1.qualifier will soon require org.eclipse.angularjs.jsp.core [1.0.0] but it's not (yet) in the AngularJS mirror. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 14:27:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 14:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21014) Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21014: ---------------------------------- Assignee: Alexey Kazakov (was: Nick Boldt) > Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins > ---------------------------------------------------------------------------- > > Key: JBIDE-21014 > URL: https://issues.jboss.org/browse/JBIDE-21014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, updatesite, upstream > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > org.jboss.tools.jst.angularjs.test 3.7.1.qualifier will soon require org.eclipse.angularjs.jsp.core [1.0.0] but it's not (yet) in the AngularJS mirror. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 14:30:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 14:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21014) Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBIDE-21014. -------------------------------- Resolution: Done I've updated this mirror [1] so that we can decide to include / depend on more stuff. [1] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0.201508312121/ Then... [~akazakov] said: {quote} (2015-10-23 14:20:47) akazakov: nickboldt, we need the same we install via EA (2015-10-23 14:21:28) nickboldt: akazakov: the EA install only includes one feature... (2015-10-23 14:21:48) nickboldt: angularjs-eclipse-feature (2015-10-23 14:22:06) akazakov: so, any problem with that? (2015-10-23 14:22:15) nickboldt: https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery.earlyaccess/plugin.xml#L41 (2015-10-23 14:22:27) nickboldt: well, no... but you asked for another plugin which isn't part of that feature (2015-10-23 14:22:42) akazakov: hm (2015-10-23 14:23:34) nickboldt: angularjs-eclipse-jsp-feature != angularjs-eclipse-feature (2015-10-23 14:23:56) akazakov: nickboldt, that's my fault (2015-10-23 14:24:37) akazakov: nickboldt, didn't notice that I included jsp.core instead of core (2015-10-23 14:24:44) nickboldt: gah (2015-10-23 14:24:53) nickboldt: so you DON'T need the jsp feature? (2015-10-23 14:24:58) akazakov: no :) {quote} Which means we probably don't need the extra stuff on this site. So I won't update the EA site to include more stuff yet. > Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins > ---------------------------------------------------------------------------- > > Key: JBIDE-21014 > URL: https://issues.jboss.org/browse/JBIDE-21014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, updatesite, upstream > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > org.jboss.tools.jst.angularjs.test 3.7.1.qualifier will soon require org.eclipse.angularjs.jsp.core [1.0.0] but it's not (yet) in the AngularJS mirror. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 14:32:03 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 14:32:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21014) Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-21014. ---------------------------------- Yes, I added a dependency to the wrong angularjs plugin. Updated the corresponding PRs. Sorry for that. Closing. > Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins > ---------------------------------------------------------------------------- > > Key: JBIDE-21014 > URL: https://issues.jboss.org/browse/JBIDE-21014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, updatesite, upstream > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > org.jboss.tools.jst.angularjs.test 3.7.1.qualifier will soon require org.eclipse.angularjs.jsp.core [1.0.0] but it's not (yet) in the AngularJS mirror. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 14:32:08 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 14:32:08 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21014) Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov closed JBIDE-21014. ---------------------------------- Resolution: Rejected > Need complete mirror of AngularJS 1.0.0 so jst tests can depend more plugins > ---------------------------------------------------------------------------- > > Key: JBIDE-21014 > URL: https://issues.jboss.org/browse/JBIDE-21014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, updatesite, upstream > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > org.jboss.tools.jst.angularjs.test 3.7.1.qualifier will soon require org.eclipse.angularjs.jsp.core [1.0.0] but it's not (yet) in the AngularJS mirror. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-17882) Validate remote server dir before start/stop/deploy operations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-17882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-17882: ----------------------------------- Fix Version/s: 4.3.x 4.4.x (was: 4.3.1.Beta1) > Validate remote server dir before start/stop/deploy operations > -------------------------------------------------------------- > > Key: JBIDE-17882 > URL: https://issues.jboss.org/browse/JBIDE-17882 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.x > > > Max said this on irc today: > {quote} > strykerawb: i got some really weird behavior 12:56:27 > maxandersen strykerawb: see this video: http://screencast.com/t/uSDT1EoS 12:56:31 > jbossbot Title: 014-07-15_1255 - max.rydahl.andersen's library 12:56:31 > maxandersen what is it doing? 12:56:34 > maxandersen this is me dragging a project to wildfly server 12:56:42 > maxandersen ah the server is configured as remote with blank remote server home... 12:57:05 > maxandersen seems that result in complete funky endless loop.. > {quote} > The problem is that he had an empty dir set up on a remote server. So when he tried to publish, this resulted in some unexpected behavior (endless copy progress in this case). > Currently, when you create a remote server, the dialog will not let you leave the server home dir empty. But that is not enough. You can still change it in the server editor to be empty. Rob says he wants to remove this field from the server editor and only use the wizard, but that is still not enough - the user can remote the folder on the remote system at a later time. > We probably don't need to check the folder every time we use it, but at least at the start of each operation such as start/stop server, publish to server. > Also, the New server dialog checks for empty string, but I'm not 100 % sure if it actually checks that the folder exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:07:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-17882) Validate remote server dir before start/stop/deploy operations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-17882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-17882: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) > Validate remote server dir before start/stop/deploy operations > -------------------------------------------------------------- > > Key: JBIDE-17882 > URL: https://issues.jboss.org/browse/JBIDE-17882 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > > Max said this on irc today: > {quote} > strykerawb: i got some really weird behavior 12:56:27 > maxandersen strykerawb: see this video: http://screencast.com/t/uSDT1EoS 12:56:31 > jbossbot Title: 014-07-15_1255 - max.rydahl.andersen's library 12:56:31 > maxandersen what is it doing? 12:56:34 > maxandersen this is me dragging a project to wildfly server 12:56:42 > maxandersen ah the server is configured as remote with blank remote server home... 12:57:05 > maxandersen seems that result in complete funky endless loop.. > {quote} > The problem is that he had an empty dir set up on a remote server. So when he tried to publish, this resulted in some unexpected behavior (endless copy progress in this case). > Currently, when you create a remote server, the dialog will not let you leave the server home dir empty. But that is not enough. You can still change it in the server editor to be empty. Rob says he wants to remove this field from the server editor and only use the wizard, but that is still not enough - the user can remote the folder on the remote system at a later time. > We probably don't need to check the folder every time we use it, but at least at the start of each operation such as start/stop server, publish to server. > Also, the New server dialog checks for empty string, but I'm not 100 % sure if it actually checks that the folder exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:08:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-9442) Investigate possibility for remote debug launch of app servers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-9442: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.Beta1) > Investigate possibility for remote debug launch of app servers > -------------------------------------------------------------- > > Key: JBIDE-9442 > URL: https://issues.jboss.org/browse/JBIDE-9442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.x > > > When launching a remote server on a remote host, we do not currently connect a remote debugger. It'd be nice if we also connected a remote debugger if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:09:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 15:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20946) New Application wizard: Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20946: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-20946 > URL: https://issues.jboss.org/browse/JBIDE-20946 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:09:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 15:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21015) New Application wizard: Add multi-tag filtering to templates In-Reply-To: References: Message-ID: Fred Bricon created JBIDE-21015: ----------------------------------- Summary: New Application wizard: Add multi-tag filtering to templates Key: JBIDE-21015 URL: https://issues.jboss.org/browse/JBIDE-21015 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Final Reporter: Jeff Cantrill Assignee: Fred Bricon Priority: Optional Fix For: 4.4.0.Alpha1 Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:09:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 15:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21015) New Application wizard: Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-21015: -------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.4.0.Alpha1) > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-21015 > URL: https://issues.jboss.org/browse/JBIDE-21015 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:10:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 15:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21015) New Application wizard: Add multi-tag filtering to templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-21015. --------------------------------- Resolution: Done Fixed in 4.3.x > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-21015 > URL: https://issues.jboss.org/browse/JBIDE-21015 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:12:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20798) log filling up with "unable to retrieve a list of remote deployments" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20798: ----------------------------------- Fix Version/s: 4.3.x 4.4.x (was: 4.3.1.Beta1) > log filling up with "unable to retrieve a list of remote deployments" > --------------------------------------------------------------------- > > Key: JBIDE-20798 > URL: https://issues.jboss.org/browse/JBIDE-20798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.x > > Attachments: Java_EE_-_JBoss_EAP_6_4_-_Eclipse_-__Users_max_Documents_workspace-deploy-demo.png > > > when starting/stopping EAP 6.4 server I 'm getting my logs filled with: > {code} > Unable to retrieve a list of remote deployment scanners > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [ > {"subsystem" => "deployment-scanner"}, > {"scanner" => "*"} > ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available". > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361) > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:236) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:234) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:122) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDefaultDeploymentScanner(AS7DeploymentScannerUtility.java:212) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadDefaultScannerFromServer(LocalJBoss7DeploymentScannerAdditions.java:148) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersAdded(LocalJBoss7DeploymentScannerAdditions.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.updateDeploymentScanners(AbstractDeploymentScannerAdditions.java:61) > at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions$1.run(AbstractDeploymentScannerAdditions.java:74) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [ > {"subsystem" => "deployment-scanner"}, > {"scanner" => "*"} > ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available". > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352) > ... 15 more > {code} > since these are done during startup and it is possible to see in the error then I would expect we did not log this by default for this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:14:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20588) JBoss Modules classpath: show suggested modules without using Ctrl+space In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20588: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) (was: 4.3.1.Beta1) > JBoss Modules classpath: show suggested modules without using Ctrl+space > ------------------------------------------------------------------------ > > Key: JBIDE-20588 > URL: https://issues.jboss.org/browse/JBIDE-20588 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.x > > > This is a follow-up of JBIDE-19799. > In Eclipse > preferences > Server > Runtime Environments > Default Classpath Entries > you can add new classpath entries. For AS7 and newer servers, the main mechanism is using JBoss Modules. > So when you choose your server type and then Add -> JBoss Module, in the dialog, there is a field called Module ID. In JBIDE-19799, a possibility was added to show suggestions based on what you start typing - it's using content assist. > Would it be possible to start suggesting right away, i.e. without using Ctrl+space? Content Assist is not really something one would expect in a dialog, so it may be a bit counter-intuitive. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:16:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20740) Change of JVM Monitor "Period to Search JVMs on local host" takes effect only after eclipse restart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20740: ----------------------------------- Fix Version/s: 4.3.x 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Change of JVM Monitor "Period to Search JVMs on local host" takes effect only after eclipse restart > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20740 > URL: https://issues.jboss.org/browse/JBIDE-20740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:20:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20713) Ensure follow-redirects patch is accepted into upstream Mars.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121728#comment-13121728 ] Alexey Kazakov commented on JBIDE-20713: ---------------------------------------- >From https://bugs.eclipse.org/bugs/show_bug.cgi?id=474741#c10 "Since maintenance wasn't branched yet, this push to master is effectively in both streams." Resolving for 4.3.1. > Ensure follow-redirects patch is accepted into upstream Mars.2 > -------------------------------------------------------------- > > Key: JBIDE-20713 > URL: https://issues.jboss.org/browse/JBIDE-20713 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Final > > > Ensure that the upstream patch to follow redirects is committed before SR2. https://bugs.eclipse.org/bugs/show_bug.cgi?id=473971 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:20:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20713) Ensure follow-redirects patch is accepted into upstream Mars.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20713. ------------------------------------ Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) Resolution: Done > Ensure follow-redirects patch is accepted into upstream Mars.2 > -------------------------------------------------------------- > > Key: JBIDE-20713 > URL: https://issues.jboss.org/browse/JBIDE-20713 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Final > > > Ensure that the upstream patch to follow redirects is committed before SR2. https://bugs.eclipse.org/bugs/show_bug.cgi?id=473971 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20830: ----------------------------------- Fix Version/s: 4.3.0.Final (was: 4.3.1.Beta1) > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Final > > Attachments: screenshot.png > > > h2. Offending ejb-jar.xml > If you have the following {{ejb-jar.xml}}, which I got from [this Wildfly Wiki page|https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference]: > {code:xml} > > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > > > ReplyingMDB > org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB > > > destination > java:jboss/mdbtest/messageDestinationQueue > > > > > > > > DDMyDomainSFSB > myDomain > myPrincipal > > > > {code} > h2. Errors/Warnings > You'll get a few warnings: > !screenshot.png! > In the console: > {noformat} > Description Resource Path Location Type > Referenced file contains errors (jar:file:/Users/me/Applications/sts-bundle/STS.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150723-0026-B29.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /my-project/src/main/resources/META-INF line 1 XML Problem > {noformat} > h2. Related issues > * https://bugzilla.redhat.com/show_bug.cgi?id=1193543 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121730#comment-13121730 ] Alexey Kazakov commented on JBIDE-20830: ---------------------------------------- The upstream patch has been accepted - JBIDE-20713 We should verify this issue as soon as we upgrade JBT 4.3.1 Target Platform to Eclipse Mars.2 (will happen after 4.3.1.Beta1 release probably). > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Final > > Attachments: screenshot.png > > > h2. Offending ejb-jar.xml > If you have the following {{ejb-jar.xml}}, which I got from [this Wildfly Wiki page|https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference]: > {code:xml} > > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > > > ReplyingMDB > org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB > > > destination > java:jboss/mdbtest/messageDestinationQueue > > > > > > > > DDMyDomainSFSB > myDomain > myPrincipal > > > > {code} > h2. Errors/Warnings > You'll get a few warnings: > !screenshot.png! > In the console: > {noformat} > Description Resource Path Location Type > Referenced file contains errors (jar:file:/Users/me/Applications/sts-bundle/STS.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150723-0026-B29.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /my-project/src/main/resources/META-INF line 1 XML Problem > {noformat} > h2. Related issues > * https://bugzilla.redhat.com/show_bug.cgi?id=1193543 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:28:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20337) Add unit tests for exploded utility projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20337: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Add unit tests for exploded utility projects > -------------------------------------------- > > Key: JBIDE-20337 > URL: https://issues.jboss.org/browse/JBIDE-20337 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.Final > > > Add unit tests for the logic change in JBIDE-15250 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:34:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 15:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-21016: ---------------------------------- Summary: compile failed in openshift Key: JBIDE-21016 URL: https://issues.jboss.org/browse/JBIDE-21016 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Nick Boldt Priority: Blocker Denis says Openshift is failing to compile: {code} [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: [INFO] [ERROR] :[41] [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); [INFO] [ERROR] ^^^^^^^^^^^^^^^^ [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field [INFO] [ERROR] 1 problem (1 error){code} Jenkins says something else: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] [ERROR] private IObservableList mutableTargets = new WritableList<>(); [ERROR] ^^^^^^^^^^^^ [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:35:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 15:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21016: ------------------------------- Description: Denis says Openshift is failing to compile in master: {code} [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: [INFO] [ERROR] :[41] [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); [INFO] [ERROR] ^^^^^^^^^^^^^^^^ [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console Different compilation failure in 4.3.x: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] [ERROR] private IObservableList mutableTargets = new WritableList<>(); [ERROR] ^^^^^^^^^^^^ [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console was: Denis says Openshift is failing to compile: {code} [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: [INFO] [ERROR] :[41] [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); [INFO] [ERROR] ^^^^^^^^^^^^^^^^ [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field [INFO] [ERROR] 1 problem (1 error){code} Jenkins says something else: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] [ERROR] private IObservableList mutableTargets = new WritableList<>(); [ERROR] ^^^^^^^^^^^^ [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Priority: Blocker > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:35:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 15:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21016: ------------------------------- Affects Version/s: 4.4.0.Alpha1 > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Priority: Blocker > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:35:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 15:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21016: ---------------------------------- Assignee: Nick Boldt > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:35:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 23 Oct 2015 15:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21016: ---------------------------------- Assignee: Fred Bricon (was: Nick Boldt) > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 15:37:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 15:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21016: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:43:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121745#comment-13121745 ] Andre Dietisheim commented on JBIDE-20849: ------------------------------------------ We discussed this and agreed to exclude the empty widgets from layouting which results in having no empty space if there's no signup link or userdoc. > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:47:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121746#comment-13121746 ] Andre Dietisheim commented on JBIDE-20849: ------------------------------------------ merged and pushed to upstream/jbosstools-4.3.x > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:47:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21017) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21017: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-21017 > URL: https://issues.jboss.org/browse/JBIDE-21017 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Mari?n Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.0.Alpha1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:47:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21017) Blank space in a New Connection dialog In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-21017: ---------------------------------------- Summary: Blank space in a New Connection dialog Key: JBIDE-21017 URL: https://issues.jboss.org/browse/JBIDE-21017 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.CR2 Reporter: Mari?n Labuda Assignee: Andre Dietisheim Priority: Minor Fix For: 4.3.1.Beta1 There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. !openshift2_connection_dialog.png! !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:51:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim reassigned JBIDE-21016: ---------------------------------------- Assignee: Andre Dietisheim (was: Fred Bricon) > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:52:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: Andre Dietisheim created JBIDE-21018: ---------------------------------------- Summary: compile failed in openshift Key: JBIDE-21018 URL: https://issues.jboss.org/browse/JBIDE-21018 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 Reporter: Nick Boldt Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 Denis says Openshift is failing to compile in master: {code} [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: [INFO] [ERROR] :[41] [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); [INFO] [ERROR] ^^^^^^^^^^^^^^^^ [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console Different compilation failure in 4.3.x: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] [ERROR] private IObservableList mutableTargets = new WritableList<>(); [ERROR] ^^^^^^^^^^^^ [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:53:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21016: ------------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:53:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 16:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20802) jax-rs refresh triggers error in server.launchbar on kitchensink example with launchbar wtp installed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20802: ----------------------------------- Fix Version/s: 4.3.1.Final 4.4.0.Alpha1 (was: 4.3.1.Beta1) > jax-rs refresh triggers error in server.launchbar on kitchensink example with launchbar wtp installed > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20802 > URL: https://issues.jboss.org/browse/JBIDE-20802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > Have jboss launchbar tooling installed and then : > use the kitchensink example (JAvaEE project). > project shows up with blank/empty JAX-RS Web services node > Right click and refresh the resources > I then browse the tree and in logs I get: > {code} > java.lang.ClassCastException: org.jboss.tools.ws.jaxrs.ui.internal.launcher.JaxrsEndpointModuleArtifact cannot be cast to org.eclipse.wst.server.core.model.ModuleArtifactDelegate > at org.jboss.tools.wtp.server.launchbar.objects.ModuleArtifactWrapper.getName(ModuleArtifactWrapper.java:36) > at org.jboss.tools.wtp.server.launchbar.descriptors.ModuleArtifactLaunchDescriptor.getName(ModuleArtifactLaunchDescriptor.java:45) > at org.eclipse.launchbar.core.internal.LaunchBarManager.getDescriptorId(LaunchBarManager.java:293) > at org.eclipse.launchbar.core.internal.LaunchBarManager.addDescriptor(LaunchBarManager.java:301) > at org.eclipse.launchbar.core.internal.LaunchBarManager.launchObjectAdded(LaunchBarManager.java:342) > at org.jboss.tools.wtp.server.launchbar.ModuleObjectProvider.selectionChanged(ModuleObjectProvider.java:331) > at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:237) > at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:122) > at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$1(SelectionService.java:112) > at org.eclipse.ui.internal.e4.compatibility.SelectionService$3.selectionChanged(SelectionService.java:80) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:167) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:164) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:161) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:273) > at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:270) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114) > at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341) > at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356) > at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:132) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:877) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:874) > at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1243) > at org.eclipse.ui.navigator.CommonViewer.handlePostSelect(CommonViewer.java:455) > at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1269) > at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265) > at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259) > at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > 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:483) > 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) > {code} > then when I start clicking around and try working I get error dialogs popping up. > Looks like it tries to convert things it should not try converting. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:53:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21016: ------------------------------------- Description: Compilation failure in 4.3.x: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] [ERROR] private IObservableList mutableTargets = new WritableList<>(); [ERROR] ^^^^^^^^^^^^ [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console was: Denis says Openshift is failing to compile in master: {code} [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: [INFO] [ERROR] :[41] [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); [INFO] [ERROR] ^^^^^^^^^^^^^^^^ [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console Different compilation failure in 4.3.x: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] [ERROR] private IObservableList mutableTargets = new WritableList<>(); [ERROR] ^^^^^^^^^^^^ [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > Compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:53:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21018: ------------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > Different compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 16:54:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 16:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21018: ------------------------------------- Description: Denis says Openshift is failing to compile in master: {code} [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: [INFO] [ERROR] :[41] [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); [INFO] [ERROR] ^^^^^^^^^^^^^^^^ [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console {code} was: Denis says Openshift is failing to compile in master: {code} [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: [INFO] [ERROR] :[41] [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); [INFO] [ERROR] ^^^^^^^^^^^^^^^^ [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console Different compilation failure in 4.3.x: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] [ERROR] private IObservableList mutableTargets = new WritableList<>(); [ERROR] ^^^^^^^^^^^^ [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:01:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 17:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20845: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:01:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 17:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121748#comment-13121748 ] Max Rydahl Andersen commented on JBIDE-21012: --------------------------------------------- deploy to nexus is interesting because it would be much simpler to use rather than manually copying around sites on jboss.org. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:02:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Fri, 23 Oct 2015 17:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121748#comment-13121748 ] Max Rydahl Andersen edited comment on JBIDE-21012 at 10/23/15 5:01 PM: ----------------------------------------------------------------------- deploy to nexus is interesting because it should be much simpler to use rather than manually copying around sites on jboss.org. was (Author: maxandersen): deploy to nexus is interesting because it would be much simpler to use rather than manually copying around sites on jboss.org. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:02:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 17:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121749#comment-13121749 ] Alexey Kazakov commented on JBIDE-20845: ---------------------------------------- [~snjeza] could you please take a look? > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:04:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 17:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21016: ------------------------------------- Affects Version/s: (was: 4.4.0.Alpha1) > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > Compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:04:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 17:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim updated JBIDE-21018: ------------------------------------- Affects Version/s: (was: 4.3.1.Beta1) > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:14:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 17:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre Dietisheim reassigned JBIDE-21016: ---------------------------------------- Assignee: Fred Bricon (was: Andre Dietisheim) > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > Compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:15:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 17:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121750#comment-13121750 ] Andre Dietisheim commented on JBIDE-21016: ------------------------------------------ [~fbricon] fixed this in jbosstools-4.3.x > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > Compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:15:01 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 23 Oct 2015 17:15:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21016) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon resolved JBIDE-21016. --------------------------------- Resolution: Done fixed in 4.3.x > compile failed in openshift > --------------------------- > > Key: JBIDE-21016 > URL: https://issues.jboss.org/browse/JBIDE-21016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > Compilation failure in 4.3.x: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615] > [ERROR] private IObservableList mutableTargets = new WritableList<>(); > [ERROR] ^^^^^^^^^^^^ > [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <> > [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/59/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:19:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 17:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20753: ----------------------------------- Fix Version/s: 4.3.x 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Text flickering when selecting server types in New Server wizard > ---------------------------------------------------------------- > > Key: JBIDE-20753 > URL: https://issues.jboss.org/browse/JBIDE-20753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: regression > Fix For: 4.3.x, 4.4.0.Alpha1 > > > When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog. > I checked and this did not happen in Beta2. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:21:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 17:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20910) XLabelProvider$RootWrapper memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20910: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > XLabelProvider$RootWrapper memory leak > -------------------------------------- > > Key: JBIDE-20910 > URL: https://issues.jboss.org/browse/JBIDE-20910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.x, 4.4.0.Alpha1 > > > I see amount of XLabelProvider$RootWrapper instances just raising in numbers when importing/deleting projects -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:28:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 23 Oct 2015 17:28:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20700) JBoss Knowledge Base Builder hangs up In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBIDE-20700. ------------------------------------ Fix Version/s: 4.3.0.CR2 (was: 4.4.0.Alpha1) (was: 4.3.1.Beta1) Resolution: Duplicate Issue Resolving as a duplicate. Please re-open if it's still an issue in JBoss Tools 4.3.0.Final. We will create a separate issue for KB Builder - > Cancel button. > JBoss Knowledge Base Builder hangs up > ------------------------------------- > > Key: JBIDE-20700 > URL: https://issues.jboss.org/browse/JBIDE-20700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta2 > Environment: Windows 10 > JDK 8 > Eclipse Mars > JBoss Tools 4.3.0beta2 (the one from marketplace) > Reporter: Archimedes Trajano > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.CR2 > > > When loading up a multi-module Maven project with EAR, WAR and jar components on a fresh installation of Eclipse where the following have been added > * Tycho Project Configurator > * EclEmma > * JBoss Tools 4.3.0Beta2 > I am getting Eclipse hanging on *Invoking JBoss Knowledge Base Builder*. Clicking on cancel does not cancel the operation either. > The workaround is to disable the *JBoss Knowledge Base* in each WAR and JAR project. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:38:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 17:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121755#comment-13121755 ] Andre Dietisheim commented on JBIDE-21018: ------------------------------------------ The compilation failure can be fixed by replacing {code} Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) {code} by {code} RepositoryUtil.getDefaultRepositoryDir() {code} but then our test start to fail. > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:43:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 17:43:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121755#comment-13121755 ] Andre Dietisheim edited comment on JBIDE-21018 at 10/23/15 5:42 PM: -------------------------------------------------------------------- The compilation failure can be fixed by replacing {code} Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) {code} by {code} RepositoryUtil.getDefaultRepositoryDir() {code} but then our test start to fail: {code} ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.tools.openshift.egit.internal.test.EGitTestSuite SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Tests run: 60, Failures: 0, Errors: 54, Skipped: 0, Time elapsed: 8.554 sec <<< FAILURE! - in org.jboss.tools.openshift.egit.internal.test.EGitTestSuite canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.965 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.974 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.162 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.163 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.176 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.176 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.186 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.186 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.224 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.225 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.179 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.18 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.168 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.168 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) changedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.203 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) changedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.203 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.205 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.206 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.193 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.194 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.206 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.207 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.174 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.175 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.172 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.173 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.079 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.08 sec <<< ERROR! java.io.IOException: Could not delete file /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/tests/org.jboss.tools.openshift.egit.test/target/work/data/Project-1445636467448 at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:197) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.remove(TestRepository.java:520) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.dispose(TestRepository.java:512) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:95) modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.18 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.181 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.192 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.193 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.233 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.233 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.215 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.216 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.17 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.171 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.143 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.144 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.069 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.07 sec <<< ERROR! java.io.IOException: Could not delete file /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/tests/org.jboss.tools.openshift.egit.test/target/work/data/Project-1445636469669 at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:197) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.remove(TestRepository.java:520) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.dispose(TestRepository.java:512) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:95) fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.33 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.331 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.166 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.166 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.183 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.184 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.221 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.222 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.239 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.24 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.213 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.214 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canAddEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.026 sec writingDoesNotAlterOrdering(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.233 sec canParseExistingEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.067 sec newEntriesAreAddedToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.073 sec addingExistingEntryDoesNotMoveItToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.076 sec entryIsNotAddedTwice(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.087 sec Results : Tests in error: EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:95 ? IO Could not delete file /home/adietish/jboss-work... EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:95 ? IO Could not delete file /home/adietish/jboss-work... EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer Tests run: 60, Failures: 0, Errors: 54, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jbosstools-openshift ............................... SUCCESS [ 0.653 s] [INFO] openshift.plugins .................................. SUCCESS [ 0.042 s] [INFO] org.jboss.tools.openshift.egit.core ................ SUCCESS [ 10.752 s] [INFO] org.jboss.tools.openshift.egit.ui .................. SUCCESS [ 0.638 s] [INFO] org.jboss.tools.openshift.express.client ........... SUCCESS [ 1.278 s] [INFO] org.jboss.tools.openshift.common.core .............. SUCCESS [ 1.599 s] [INFO] org.jboss.tools.openshift.express.core ............. SUCCESS [ 1.615 s] [INFO] org.jboss.tools.openshift.common.ui ................ SUCCESS [ 1.962 s] [INFO] org.jboss.tools.openshift.express.ui ............... SUCCESS [ 3.890 s] [INFO] org.jboss.tools.openshift.client ................... SUCCESS [ 0.970 s] [INFO] org.jboss.tools.openshift.core ..................... SUCCESS [ 0.727 s] [INFO] org.jboss.tools.openshift.ui ....................... SUCCESS [ 2.766 s] [INFO] openshift.tests .................................... SUCCESS [ 0.015 s] [INFO] org.jboss.tools.openshift.egit.test ................ FAILURE [ 32.192 s] [INFO] org.jboss.tools.openshift.express.test ............. SKIPPED [INFO] org.jboss.tools.openshift.test ..................... SKIPPED [INFO] openshift.features ................................. SKIPPED [INFO] org.jboss.tools.openshift.feature .................. SKIPPED [INFO] org.jboss.tools.openshift.test.feature ............. SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.feature . SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.test.feature SKIPPED [INFO] org.jboss.tools.openshift.express.feature .......... SKIPPED [INFO] org.jboss.tools.openshift.express.test.feature ..... SKIPPED [INFO] openshift.site ..................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ {code} was (Author: adietish): The compilation failure can be fixed by replacing {code} Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) {code} by {code} RepositoryUtil.getDefaultRepositoryDir() {code} but then our test start to fail. > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 17:46:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 17:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121755#comment-13121755 ] Andre Dietisheim edited comment on JBIDE-21018 at 10/23/15 5:45 PM: -------------------------------------------------------------------- The compilation failure can be fixed by replacing {code} Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) {code} by {code} RepositoryUtil.getDefaultRepositoryDir() {code} as stated in the following bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=395143 but then our test start to fail: {code} ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.tools.openshift.egit.internal.test.EGitTestSuite SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Tests run: 60, Failures: 0, Errors: 54, Skipped: 0, Time elapsed: 8.554 sec <<< FAILURE! - in org.jboss.tools.openshift.egit.internal.test.EGitTestSuite canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.965 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.974 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.162 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.163 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.176 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.176 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.186 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.186 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.224 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.225 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.179 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.18 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.168 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.168 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) changedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.203 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) changedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.203 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.205 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.206 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.193 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.194 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.206 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.207 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.174 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.175 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.172 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.173 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.079 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.08 sec <<< ERROR! java.io.IOException: Could not delete file /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/tests/org.jboss.tools.openshift.egit.test/target/work/data/Project-1445636467448 at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:197) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.remove(TestRepository.java:520) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.dispose(TestRepository.java:512) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:95) modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.18 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.181 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.192 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.193 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.233 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.233 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.215 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.216 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.17 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.171 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.143 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.144 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.069 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.07 sec <<< ERROR! java.io.IOException: Could not delete file /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/tests/org.jboss.tools.openshift.egit.test/target/work/data/Project-1445636469669 at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:197) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.remove(TestRepository.java:520) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.dispose(TestRepository.java:512) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:95) fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.33 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.331 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.166 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.166 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.183 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.184 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.221 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.222 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.239 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.24 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.213 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.214 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canAddEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.026 sec writingDoesNotAlterOrdering(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.233 sec canParseExistingEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.067 sec newEntriesAreAddedToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.073 sec addingExistingEntryDoesNotMoveItToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.076 sec entryIsNotAddedTwice(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.087 sec Results : Tests in error: EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:95 ? IO Could not delete file /home/adietish/jboss-work... EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:95 ? IO Could not delete file /home/adietish/jboss-work... EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer Tests run: 60, Failures: 0, Errors: 54, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jbosstools-openshift ............................... SUCCESS [ 0.653 s] [INFO] openshift.plugins .................................. SUCCESS [ 0.042 s] [INFO] org.jboss.tools.openshift.egit.core ................ SUCCESS [ 10.752 s] [INFO] org.jboss.tools.openshift.egit.ui .................. SUCCESS [ 0.638 s] [INFO] org.jboss.tools.openshift.express.client ........... SUCCESS [ 1.278 s] [INFO] org.jboss.tools.openshift.common.core .............. SUCCESS [ 1.599 s] [INFO] org.jboss.tools.openshift.express.core ............. SUCCESS [ 1.615 s] [INFO] org.jboss.tools.openshift.common.ui ................ SUCCESS [ 1.962 s] [INFO] org.jboss.tools.openshift.express.ui ............... SUCCESS [ 3.890 s] [INFO] org.jboss.tools.openshift.client ................... SUCCESS [ 0.970 s] [INFO] org.jboss.tools.openshift.core ..................... SUCCESS [ 0.727 s] [INFO] org.jboss.tools.openshift.ui ....................... SUCCESS [ 2.766 s] [INFO] openshift.tests .................................... SUCCESS [ 0.015 s] [INFO] org.jboss.tools.openshift.egit.test ................ FAILURE [ 32.192 s] [INFO] org.jboss.tools.openshift.express.test ............. SKIPPED [INFO] org.jboss.tools.openshift.test ..................... SKIPPED [INFO] openshift.features ................................. SKIPPED [INFO] org.jboss.tools.openshift.feature .................. SKIPPED [INFO] org.jboss.tools.openshift.test.feature ............. SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.feature . SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.test.feature SKIPPED [INFO] org.jboss.tools.openshift.express.feature .......... SKIPPED [INFO] org.jboss.tools.openshift.express.test.feature ..... SKIPPED [INFO] openshift.site ..................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ {code} was (Author: adietish): The compilation failure can be fixed by replacing {code} Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) {code} by {code} RepositoryUtil.getDefaultRepositoryDir() {code} but then our test start to fail: {code} ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.tools.openshift.egit.internal.test.EGitTestSuite SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Tests run: 60, Failures: 0, Errors: 54, Skipped: 0, Time elapsed: 8.554 sec <<< FAILURE! - in org.jboss.tools.openshift.egit.internal.test.EGitTestSuite canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.965 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.974 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.162 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.163 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.176 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.176 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.186 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.186 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.224 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.225 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.179 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.18 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.168 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.168 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) changedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.203 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) changedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.203 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.205 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.206 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.193 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.194 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.206 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.207 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.174 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.175 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.172 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.173 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.079 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.08 sec <<< ERROR! java.io.IOException: Could not delete file /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/tests/org.jboss.tools.openshift.egit.test/target/work/data/Project-1445636467448 at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:197) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.remove(TestRepository.java:520) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.dispose(TestRepository.java:512) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:95) modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.18 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.181 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.192 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.193 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.233 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.233 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.215 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.216 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.17 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.171 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.143 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.144 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.069 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.07 sec <<< ERROR! java.io.IOException: Could not delete file /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/tests/org.jboss.tools.openshift.egit.test/target/work/data/Project-1445636469669 at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:197) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.remove(TestRepository.java:520) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.dispose(TestRepository.java:512) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:95) fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.33 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.331 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.166 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.166 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.183 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.184 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.221 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.222 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.239 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.24 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.213 sec <<< ERROR! org.eclipse.core.runtime.CoreException: Connecting Git team provider failed. See log for details. at org.eclipse.egit.core.op.ConnectProviderOperation.execute(ConnectProviderOperation.java:111) at org.jboss.tools.openshift.egit.internal.test.util.TestRepository.connect(TestRepository.java:533) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.createTestRepository(EGitUtilsTest.java:79) at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.setUp(EGitUtilsTest.java:71) fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.214 sec <<< ERROR! java.lang.NullPointerException: null at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:97) canAddEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.026 sec writingDoesNotAlterOrdering(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.233 sec canParseExistingEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.067 sec newEntriesAreAddedToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.073 sec addingExistingEntryDoesNotMoveItToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.076 sec entryIsNotAddedTwice(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.087 sec Results : Tests in error: EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:95 ? IO Could not delete file /home/adietish/jboss-work... EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:95 ? IO Could not delete file /home/adietish/jboss-work... EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer EGitUtilsTest.setUp:71->createTestRepository:79 ? Core Connecting Git team pro... EGitUtilsTest.tearDown:97 NullPointer Tests run: 60, Failures: 0, Errors: 54, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jbosstools-openshift ............................... SUCCESS [ 0.653 s] [INFO] openshift.plugins .................................. SUCCESS [ 0.042 s] [INFO] org.jboss.tools.openshift.egit.core ................ SUCCESS [ 10.752 s] [INFO] org.jboss.tools.openshift.egit.ui .................. SUCCESS [ 0.638 s] [INFO] org.jboss.tools.openshift.express.client ........... SUCCESS [ 1.278 s] [INFO] org.jboss.tools.openshift.common.core .............. SUCCESS [ 1.599 s] [INFO] org.jboss.tools.openshift.express.core ............. SUCCESS [ 1.615 s] [INFO] org.jboss.tools.openshift.common.ui ................ SUCCESS [ 1.962 s] [INFO] org.jboss.tools.openshift.express.ui ............... SUCCESS [ 3.890 s] [INFO] org.jboss.tools.openshift.client ................... SUCCESS [ 0.970 s] [INFO] org.jboss.tools.openshift.core ..................... SUCCESS [ 0.727 s] [INFO] org.jboss.tools.openshift.ui ....................... SUCCESS [ 2.766 s] [INFO] openshift.tests .................................... SUCCESS [ 0.015 s] [INFO] org.jboss.tools.openshift.egit.test ................ FAILURE [ 32.192 s] [INFO] org.jboss.tools.openshift.express.test ............. SKIPPED [INFO] org.jboss.tools.openshift.test ..................... SKIPPED [INFO] openshift.features ................................. SKIPPED [INFO] org.jboss.tools.openshift.feature .................. SKIPPED [INFO] org.jboss.tools.openshift.test.feature ............. SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.feature . SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.test.feature SKIPPED [INFO] org.jboss.tools.openshift.express.feature .......... SKIPPED [INFO] org.jboss.tools.openshift.express.test.feature ..... SKIPPED [INFO] openshift.site ..................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ {code} > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 18:13:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 18:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121759#comment-13121759 ] Andre Dietisheim commented on JBIDE-21018: ------------------------------------------ jenkins build #1024 is blue again {code} Tests run: 152, Failures: 0, Errors: 0, Skipped: 1 [INFO] All tests passed! [INFO] [INFO] --- repository-utils:0.23.3-SNAPSHOT:compare-version-with-baselines (default) @ org.jboss.tools.openshift.test --- [INFO] Skipped [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] openshift.tests .................................... SUCCESS [ 0.430 s] [INFO] org.jboss.tools.openshift.egit.test ................ SUCCESS [ 16.669 s] [INFO] org.jboss.tools.openshift.express.test ............. SUCCESS [ 14.627 s] [INFO] org.jboss.tools.openshift.test ..................... SUCCESS [ 12.059 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:02 min [INFO] Finished at: 2015-10-23T18:11:08-04:00 [INFO] Final Memory: 58M/662M [INFO] ------------------------------------------------------------------------ {code} > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 18:14:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Fri, 23 Oct 2015 18:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21018) compile failed in openshift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121760#comment-13121760 ] Andre Dietisheim commented on JBIDE-21018: ------------------------------------------ merged and pushed to upstream/master > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] :[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_master/lastBuild/console > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 18:16:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 23 Oct 2015 18:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco reassigned JBIDE-16503: ------------------------------------- Assignee: Koen Aers (was: Snjezana Peco) Could you, please, review the PR? > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x, 4.4.x > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 21:21:00 2015 From: issues at jboss.org (Viacheslav Kabanovich (JIRA)) Date: Fri, 23 Oct 2015 21:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21019) Implement cancelling in Knowledge Base Builder In-Reply-To: References: Message-ID: Viacheslav Kabanovich created JBIDE-21019: --------------------------------------------- Summary: Implement cancelling in Knowledge Base Builder Key: JBIDE-21019 URL: https://issues.jboss.org/browse/JBIDE-21019 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common/jst/core Affects Versions: 4.3.0.Final Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.x -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 09:16:03 2015 From: issues at jboss.org (Hardy Ferentschik (JIRA)) Date: Sun, 25 Oct 2015 09:16:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121801#comment-13121801 ] Hardy Ferentschik commented on JBIDE-19178: ------------------------------------------- {quote} if you are being switched to another tab then rearrange your views {quote} But wouldn't it be even better, If I would not have to know on how to re-arrange tabs and views. Also per default the tab opened to the left of the explorer in the same area (bottom). {quote} truly "inlining" the properties into the tree I think will be too much overload on normal users screens. {quote} There is a risk for overload or the general problem of making it look and behave ok, but imo it might be worth it. Or asked differently, has anyone ever experimented with this idea? In the context of this explorer or maybe as part of a different plugin/integration? > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 13:00:00 2015 From: issues at jboss.org (sdfdsfdsf dsfdsfdsfdsf (JIRA)) Date: Sun, 25 Oct 2015 13:00:00 -0400 (EDT) Subject: [jbosstools-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28JBIDE-21020=29_?= =?utf-8?b?0JHQsNGA0YHQtdC70L7QvdCwIOKAkyDQrdC40LHQsNGAINGB0LzQvtGC0YA=?= =?utf-8?b?0LXRgtGMINC+0L3Qu9Cw0LnQvSDQv9GA0Y/QvNC+0Lkg0Y3RhNC40YAgMjUu?= =?utf-8?q?10=2E2015?= In-Reply-To: References: Message-ID: sdfdsfdsf dsfdsfdsfdsf created JBIDE-21020: ---------------------------------------------- Summary: ????????? ? ????? ???????? ?????? ?????? ???? 25.10.2015 Key: JBIDE-21020 URL: https://issues.jboss.org/browse/JBIDE-21020 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: sdfdsfdsf dsfdsfdsfdsf Priority: Trivial [!http://du5abruwvbky3.cloudfront.net/uploads/2014/11/27/7695a483462a0b90a27169d3d33e3779-623-302.gif!|http://rustreams.ru/online/6620-barselona-eibar-25-oktyabrya-2015-translyaciya.html] ????? ????????? ???????, ?????? ????? ???????? ?????? ????????? - ????? 25.10 ?????... ????? futlive.ru??barselona?video?smotret-onlayn.html ????????? - ????? ?????? ????? ?????????? ???????? ??????. ... ????: ????????? - ????? ?????? ?????????? ?????????: ??????. ????????? ??????? - ??? 9 ???? ??????????: 25 ??????? 2015 ?????? ?????: 20:15 ??? ?????????? ??????... ????????? - ????? ???????? ?????? ?????? ??????????... ????????? footballhd.ru?onlinevideo?barselona-eybar-smotret? ?????? ????? ?????????? ????????? - ????? ???????? 25.10.2015 ? 20:15 (???.). ???????? ?????? ????????? - ?????, ? ????? ?????? (?????? ?????) ????? ????? ????? 25 ??????? 2015. ????????? ? ????? 25.10.2015 ???????? ?????? 5 ????? ????? mega-torrent.org?load?barselona?25102015-smotret? ??????? load ? ??????? ?????? ? ???????? ? ??? ? ??????? ?????? ????????? ? ????? 25.10.2015 ???????? ?????? ?????? ???? ??????? ????? ???????. ... ???? ????????? 25 ??????? ? 20:15 ?? ??????. ???????? ?????? ????????? - ????? / 25 ??????? 2015... 19 ????? ????? videomatches.ru??online/barselona_ehjbar?2015/1-1? ????????? - ????? ??????. ???????? ?????? ????????? - ????? - ?????? ????? ?????????? ?????. Barcelona - Eibar online. ????????? - ????? (25 ??????? 2015) ?????? ??????????... 10 ????? ????? kinozadrot.net?4974-25-oktyabrya-2015.html ???: 2015 ??????: - ????: ????? ????????: - ???????? ??: 2015 ???????: ???????? ????????????: 90 ???. ? ????? ... ???????? ?????? ????????? - ????? ?????????? (25 ??????? 2015). ????????? ?????? 25 ??????? 2015: ???????? ??????... 7 ????? ????? newsrbk.ru?news/2414820-barselona?smotret-onlayn? 19:15. ?????????. ??????? ????? ????. ????????? - ...?????? ?????? ?????????? 25 ??????? 2015 4 ???? ????? soccer-world.ru?2015/10/25/barselona-eibar ????????? ??????? ????????? - ????? ???????? ?????? 25.10.2015 ?????? 25 ??????? 2015 ? 20:15 ???. ... ??? ??????????: "?????? 1", "???+?????? 2". ????????????????????: ???. ????????? - ?????: ???????? ?????? 25 ??????? 2015... soccer365.ru?live/match?barselona-smotret-onlayn/ ???????, 9-? ???, 25.10.15 20:15. ?????????. - - ?????. ... ???????: ???? ??? ?????????, ??????? +18?C ????????? ??????????. ????????? - ?????. ???????? ?????? ??????????????? 7 ????? ????? terrikon.com?posts/231765 ???????? ?????? ???????????????. "?????????" ????? ???????? "????". ??? ????? ?????????? ????? ?????? ??????? ?? ??????? ????????, ????? ???? ? ?????????? ????????????????? "?????", ??????? ? ??????? ?????? ???????? ???? ???????. ????????? - ????? (25.10.2015) ????? ????? - 25 ???????... 16 ????? ????? uznew.ru?news/barselona_ehjbar_25_10_2015_obzor? "????????? ??????? - ????????? ???? (25.10.2015) ????? ?????". ... ??? ?? ?????? ???????? ?????? ?????? ????????? ??? ???????????, ?? ????? ???????? ??????? ???, ?????? ???????? ? ????????????? ??????? ???????. ????????? - ...?????? ?????????? ????? 25.10.2015... soccerworlds.net?online/37954-barsyelona?smotret? ????????? - ?????: ?????? ??????????. 25. ... ????? ????? ???? ?????? ???? ????????? - ?????. ???? ???????? 25 ??????? 2015 ????? ?????? ???????: 21:00:00 ?????????: ????????? ??????? ?? ???????. ????????? ? ????? 25.10.2015: ???????? ?????? ??????... 16 ????? ????? footblogger.ru?barselona-ehjjbar?smotret?onlajjn? ???????? ????????? ????? ????? ?????? ??? ??????????? LEON 1.1 10 25 ??????? ?????? 100 ???????? ????????? ?? ??? ??????? ????????. ... ???????? ? ???????? 25.10.2015: ???????? ?????? ?????? ?????????? ??????? ???????. ????????? - ?????: ...?????????? ??????, 25.10.2015... soccerlivehd.com?online/10658-barsyelona?smotret? ???????? ?????? ?????? ?????????? ?????????? ????????? - ?????, ??????? ???????? 25 ??????? 2015 ? 21:00:00 ?? ???. ??????? ?????????? ? ?????? ??????????: ????????? ??????? ?? ???????. ????????? - ????? 25 ??????? 2015: ???????? ??????... 8 ????? ????? rsute.ru?novosti-futbola/43843.html ??????? ? ??????? ??????? ? ????????? - ????? 25 ??????? 2015: ???????? ??????, ??????? ?????, ?????? ??????????. ????????? - ...??????, ?????? ?????????? - 25.10.2015... SmotriSport.tv????????????????25.10.15 21:00 ????????? ????? ????: ????????? - ????? ???????? ?????? ?????????: ??????. ???????. ??????? ???? ??????????: 25 ??????? 2015 ?????? ?????: 21:00 ???. ??????. ????????? - ????? - ...25 ??????? 2015 LiveResult.ru?football/matches?Barcelona-SD_Eibar? ?????? ????????? ?????????? ????? ????????? - ?????. ???????? ?????? ? ?????? ? ????? ???????? ?????, ??????? ???? ?????. ??????? ?????? ? ?????????. ???????????, 25 ??????? 2015. "?????????" - "?????": ...????????? ??????? 25.10.2015... footboom.com?online/match/12732 ? ???????????, 25 ??????? ?? ????? FootBoom.com ????????? ??????? ?????? ?????????? "?????????" - "?????". ... ???????? ?????? ????? "?????????" - "?????" ? ????? ?????????? ???????? ?????? 25.10.2015 ? 18:00. ??????????? ? ????? ????????? - ????? 25 ??????? 2015 Football24Online.com??2015_10_25_barcelona_eibar? ?????? ?????????? ??????????? ????? ????????? ? ?????, 25 ??????? ?????? - ???????? ????????? ????? ?????????? ????? ? ??????? ???????? (HD). ?????? ????????? ?? ???? 2015 - 2016, ??? 9. ??????????? ??????? ????????? (???????... ????????? - ????? ??????? ?? ???? 25.10.2015"???? ? ?????" 14 ????? ????? sport-footbal.ru??futbol?barselona?25-10-2015.html ????????? ? ????? ??????? ?? ???? 9 ???? ?? ???? ?? ??????? ???????. ???? ????????? 25 ??????? 2015 ???? ? 20:30 ?? ??????????? ???????. ... ????????? ??????? - ?????? ?????? ?????????? SopCast ??????... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 14:25:00 2015 From: issues at jboss.org (sdfdsfdsf dsfdsfdsfdsf (JIRA)) Date: Sun, 25 Oct 2015 14:25:00 -0400 (EDT) Subject: [jbosstools-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28JBIDE-21021=29_?= =?utf-8?b?0KTQvtGA0LzRg9C70LAtMS4g0JPRgNCw0L0t0L/RgNC4INCh0KjQkCAyMDE1?= =?utf-8?b?OiDRgdC80L7RgtGA0LXRgtGMINC+0L3Qu9Cw0LnQvSDRgtGA0LDQvdGB0Ls=?= =?utf-8?b?0Y/RhtC40Y8=?= In-Reply-To: References: Message-ID: sdfdsfdsf dsfdsfdsfdsf created JBIDE-21021: ---------------------------------------------- Summary: ???????-1. ????-??? ??? 2015: ???????? ?????? ?????????? Key: JBIDE-21021 URL: https://issues.jboss.org/browse/JBIDE-21021 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: sdfdsfdsf dsfdsfdsfdsf [!http://du5abruwvbky3.cloudfront.net/uploads/2014/11/27/7695a483462a0b90a27169d3d33e3779-623-302.gif!|http://rustreams.ru/online/6621-formula-1-gran-pri-ssha-2015-translyaciya.html] ??????? 1: ???? ??? ??? | 25 ??????? 2015 ?????? ????? ?????????? ??????. ... ??????? 1. ???? ??? ??? 2015. ?? ?????? ??????. ?????????? ??????????? ????? ????? ???????????? ?????? ????? ?????. ???????-1. ???? ??? ??? 2015: ...????? ??????????... 1 ??? ????? pravda-tv.ru?2015/10/25/184142 ???????-1. ???? ??? ??? 2015: ?????. ??????????. ????? ????. ... ? ???????????, 25 ???????, ?? ????????? ??????? ??????? ? ?????? ????????? ????? 16-?? ????? ?????????? ???????-1 ??????-2015 ? ????-??? ???. ...1 / ????-??? ??? / 25 ??????? 2015 ?????? ?????????? 21 ??? ????? videomatches.ru??formula_1_gran_pri_ssha?2015/1-1? ??????? 1. ????-??? ??? ??????. ???????? ?????? ??????? 1 ????-??? ??? - ?????? ????? ??????????. Formula 1 Grand Prix of USA online. ????-??? - ??? 2015 / ???????1 / Formula 1 - Free... ????????? allsport-live.net?live.php??Grand?video?23_10_2015 ?????? ?????? ????? ?????????? ?????: ????-??? - ??? 2015. ?????????? ?????? ???????? ?????? ?????????? ?? ?????, ??????????, ????????? ??????, ????????? ??????????, ????? ?????, ??????? ? ?????? ... ?????. ??????? 1. ????. ?????????. 24.10.2015 | ???????-1 F1 | ????-??? ??? | ????????????... ????? cskanews.com??24-10-2015-formula?gran?ssha?video? ???? ?????????? ?????? ???????? ??????-??????????????? F1 2015 ???? 16 ???????? ?????? ?????? (?????, ???): ????-??? ???. ????????????. ?????? ?????????? ????????????? ?? 21:00 ?? ??????????? ???????. * * ??????? 1 ????-??? ??? 25.10.2015: ???????? ??????... 7 ????? ????? footblogger.ru?formula?gran?ssha-25-10-2015?video? ?????? ??????????<. ... ? ?????????, ?????????? ????? ????????????? ? 2015 ???? ???? ????????. ... ??, ?? ??????? ????, ?????? ?? ???????? ???? ?????????? ????????? ????-??? ???. ??????? 1 ???? ??? ??? 2015 ?????????? ? ???????? ????????? ?????? ?????? ??????? ???? ??????? vesti.ru20:29 ??????? ?????? ??? ?????? ??????", ? ?????? ????? ?????????. ??? ????????, ?????? "???????-1" ????????? ? ????? ????-??? ???. ???? ?????.Ru ????? ?????? ?????????? ??????????. ???????-1. ????-??? ???. ??????-?????????? ????? ????????... championat.com17:00 ??????? ???????-1. ????-??? ???. ??????-?????????? ???????????? championat.com19:15 ????? ????????? ??????? ?? ????-??? ??? 2015 ?. 3 ???? ????? formula1-rus.ru?novosti/986?na-gran-pri-ssha-2015? ?????????? ??????????: ???????-1 ????-??? ???. ???????? >> ?????????? ?????????? ??????-2 ???????: ???????????? - 20:55 ???????????: ????? - 21:45 (????? ??????????). ... ??????? ?????? ?? 2015 ???. ???????-1. ????-??? ??? 2015: ...?????? ??????????... 15 ????? ????? bw4u.ru?news/18/9057/ ?? ??????????, ??? ???????, 25 ??????? 2015 ???? (25.10.2015) ? 21:45 ?? ??????????? ??????? ???????? ?????? ???? ?????? ??????: ???????? ?????? ?????????? ????? ???????-1. ????-??? ??? 2015 ????? ?????, ? ??? ?????, ? ?? ??... ????-??? ??? ????????? ?????? - ?????? ??????... sovsport.ru?formula1/match-item/1_111668 ???????? I ????-??? ??? ?????????? ???????-1 ????????? 23 ??????? 2015 ?? ?????? ? ?????. ?????? ???????? 23 ??????? 2015 ? ??????? ?? 25 ??????? 2015. ??????? ??????? 56 ??????, ?????????????? 5513 ?. ?????? ????????? ??????????... ????-??? - ??? 2015 / ...?????? ????? ?????????? ?????... ????? allsport-live.net?live.php??Grand?video?24_10_2015 ...Formula 1 - Free Practice | ???????1 ?????? ?????????? ????? - ???????? ?????? - 24-10-2015. ?????? ?????? ????? ?????????? ?????: ????-??? - ??? 2015. ... ?? ?????, ??????????, ????????? ??????, ????????? ??????????, ????? ?????, ??????? ?... ???????-1. ????-??? ???. ?????? ?????????? ?????... 6 ????? ????? stadium.ru?news/25-10-2015-formula?gran-pri-ssha? ???????????? 16-?? ????? ?????????? ???? ?? ?????????? ? ?????? ????? "???????-1" ?????? 2015 ???? - ????-??? ??? - ?????????? ?? ??????????? ??-?? ?????? ???????? ???????. ??????? 1 ???? ??? ??? 25.10.2015 ???????? ??????... 15 ????? ????? investcafe.ru?blogs/23989/posts/63142 ???????-1. ????-??? ??? 2015: ???????? ?????? ... 07kbr.ru ? ??????? ?????? 10 ?. ????? - ???????-1. ????-??? ??? 2015: ???????? ?????? ?????????? ????? ????? ????? 25.10.2015, ?????????? | ??????? ? ??? ? ???????? ?????????? ??????????: ???????-1 ????-??? ??? 6 ????? ????? formula1-rus.ru?2015/10/25/ ????? ?????????????. ????????? ???? 2015 ?. ????? ????-??? ??????. 1. Mersedes 531 ????. ... admin Yandex Inktomi Spider. ?????? ????. ?????????? ??????????: ???????-1 ????-??? ???. ????????? ??????? ???????? ? ??? ??????? ??????... 9 ????? ????? 07kbr.ru?author/bw4u/feed/ ???????-1. ????-??? ??? 2015. ... ?? ??????????, ??? ???????, 25 ??????? 2015 ???? (25.10.2015) ? 21:45 ?? ??????????? ??????? ???????? ?????? ???? ?????? ??????: ???????? ?????? ?????????? ????? ???????-1. ???????-1. ????-??? ???. ??????-??????????... championat.com??news?formula-1-gran?transljacija? ???????-1. ????-??? ???. ??????-?????????? ????????????. ? ???????, 1 ??????, ?? ??????? ??????? ? ?????? ????????? ???????????? ????-??? ??? ? ???????????? ????? ???????-1 ??????-2014. ???????-1. ????-??? ???. ??????-?????????? ?????... 4 ???? ????? championat.com??news?formula-1-gran?transljacija? ????-??? ???. ??????-?????????? ????? ???????? ? 22:00. ? ???????????, 25 ???????, ?? ????????? ??????? ??????? ? ?????? ????????? ????? 16-?? ????? ?????????? ???????-1 ??????-2015 ? ????-??? ???. ???????-1. ????-??? ???. ??????-?????????? ?????... 4 ???? ????? betteam.ru?news.php?mode=2&news=1011930&vid=6 ????-??? ???. ??????-?????????? ????? ???????? ? 22:00. ? ???????????, 25 ???????, ?? ????????? ??????? ??????? ? ?????? ????????? ????? 16-?? ????? ?????????? ???????-1 ??????-2015 ? ????-??? ???. ???????-1 ????-??? ??????? 2015 ????? ??????... kinodacha.ucoz.ru?news/formula_1_gran?21_08_2015? Kinodacha - ???????????? ??? ?????? ????? ???????-1 ????-??? ??????? 2015 ????? ?????? ?????????? 23.08.2015 - ???????? ?????? ????????? ? ??????? ???????? HD 720, ?????? ??? ?????. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 16:43:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Sun, 25 Oct 2015 16:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121809#comment-13121809 ] Snjezana Peco commented on JBIDE-20845: --------------------------------------- You have to uncheck "Window>Preferences>Java>Debug>Wa&rn when unable to install breakpoint due to missing line number attributes" !lineNumber.png! In JBDS we can change the default value for this property using plugin_customization.ini. I have created the PR that changes the default value in the o.j.t.runtime.ui plugin and works in both JBDS and JBT. [~akazakov] Could you, please, review https://github.com/jbosstools/jbosstools-base/pull/459? > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 16:44:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Sun, 25 Oct 2015 16:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco updated JBIDE-20845: ---------------------------------- Attachment: lineNumber.png > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 16:45:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Sun, 25 Oct 2015 16:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121809#comment-13121809 ] Snjezana Peco edited comment on JBIDE-20845 at 10/25/15 4:44 PM: ----------------------------------------------------------------- You have to uncheck "Window>Preferences>Java>Debug>Wa&rn when unable to install breakpoint due to missing line number attributes" !lineNumber.png! In JBDS we can change the default value for this property using plugin_customization.ini. I have created the PR that changes the default value in the o.j.t.runtime.ui plugin and works in both JBDS and JBT. [~akazakov], could you, please, review https://github.com/jbosstools/jbosstools-base/pull/459? was (Author: snjeza): You have to uncheck "Window>Preferences>Java>Debug>Wa&rn when unable to install breakpoint due to missing line number attributes" !lineNumber.png! In JBDS we can change the default value for this property using plugin_customization.ini. I have created the PR that changes the default value in the o.j.t.runtime.ui plugin and works in both JBDS and JBT. [~akazakov] Could you, please, review https://github.com/jbosstools/jbosstools-base/pull/459? > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-562) OpenShift How To: Add final section to First OS App for viewing created app in browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-562: ------------------------------- Sprint: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec), 2014/S23 (8-Dec > 21-Dec), 2014/S24 (22-Dec > 04-Jan), 2015/S1 (05-Jan > 18-Jan), 2015/S2+3 (19-Jan > 15-Feb), 2015/S4 (16-Feb > 01-Mar), 2015/S5 (02-Mar > 15-Mar), 2015/S6 (16-Mar > 29-Mar), 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec), 2014/S23 (8-Dec > 21-Dec), 2014/S24 (22-Dec > 04-Jan), 2015/S1 (05-Jan > 18-Jan), 2015/S2+3 (19-Jan > 15-Feb), 2015/S4 (16-Feb > 01-Mar), 2015/S5 (02-Mar > 15-Mar), 2015/S6 (16-Mar > 29-Mar), 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > OpenShift How To: Add final section to First OS App for viewing created app in browser > -------------------------------------------------------------------------------------- > > Key: TOOLSDOC-562 > URL: https://issues.jboss.org/browse/TOOLSDOC-562 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > > See: http://tools.jboss.org/documentation/howto/openshift_firstapp.html > Source: https://github.com/jbosstools/jbosstools-website/blob/master/documentation/howto/openshift_firstapp.adoc > Before 'Terminology', add a new section with instructions for viewing the application in a browser. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-609) FeedHenry: Document how to change the splash screen In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-609: ------------------------------- Sprint: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > FeedHenry: Document how to change the splash screen > --------------------------------------------------- > > Key: TOOLSDOC-609 > URL: https://issues.jboss.org/browse/TOOLSDOC-609 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: Priority1, cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch. > This will be added to an existing article, probably as a Did You Know? Item. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-671) JBDS 9.0 GA: Openshift v3+Eclipse Install/Getting Started Documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-671: ------------------------------- Sprint: 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 17-Aug >> 30-Aug 2015-JBDS/J 3, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > JBDS 9.0 GA: Openshift v3+Eclipse Install/Getting Started Documentation > ----------------------------------------------------------------------- > > Key: TOOLSDOC-671 > URL: https://issues.jboss.org/browse/TOOLSDOC-671 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Len DiMaggio > Assignee: Misha Ali > > Document install/getting started information for Eclipse with OpenShift v3. QE team will help with this after Aug 17. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-662) Add edited Advanced Install Task instructions to related docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-662: ------------------------------- Sprint: 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > Add edited Advanced Install Task instructions to related docs > ------------------------------------------------------------- > > Key: TOOLSDOC-662 > URL: https://issues.jboss.org/browse/TOOLSDOC-662 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Add edited Advanced Install Task instructions to following related docs: > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/customer-portal/installer-src.manual-instructions.txt > 2. https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=38513&product=jbossdeveloperstudio&version=9.0.0+Beta1&downloadType=distributions -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-623: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > Add FeedHenry Information to Existing Article about Hybrid Mobile Apps > ---------------------------------------------------------------------- > > Key: TOOLSDOC-623 > URL: https://issues.jboss.org/browse/TOOLSDOC-623 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Burr Sutter > Assignee: Supriya Bharadwaj > Fix For: 4.2.3.Final > > > Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 > Description: https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-307: ------------------------------- Sprint: 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:01 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-648) JBDS-IS: Update the Install guide with info for installing JBDS IS in Eclipse when Offline In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-648: ------------------------------- Sprint: 06-Jul >> 19-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 06-Jul >> 19-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > JBDS-IS: Update the Install guide with info for installing JBDS IS in Eclipse when Offline > ------------------------------------------------------------------------------------------ > > Key: TOOLSDOC-648 > URL: https://issues.jboss.org/browse/TOOLSDOC-648 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.3.0.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > Change the info in the install JBDS IS in Eclipse when Offline section to two .zips instead of three .zips required for installing. This will change in the next version of JBDS IS that is based on JBDS 9.0.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:01 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-577) Servers How To: Configure IDE for use with Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-577: ------------------------------- Sprint: 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT (was: 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT) > Servers How To: Configure IDE for use with Docker > ------------------------------------------------- > > Key: TOOLSDOC-577 > URL: https://issues.jboss.org/browse/TOOLSDOC-577 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide > Affects Versions: 4.2.1.Final > Reporter: Michelle Murray > Assignee: Misha Ali > Labels: Basics, Docker > > For info see: > * https://goldmann.pl/blog/2013/11/20/developing-with-wildfly-jboss-developer-studio-and-docker/ > * http://www.mastertheboss.com/eclipse/jboss-eclipse/eclipse-useful-tips-and-tricks -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:46:01 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:46:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-658) JBDS-IS 8.0.2 Install Guide: Implement installation information In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-658: ------------------------------- Sprint: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 09-Nov >> 2-Nov 2015-JBDS/JBT (was: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT) > JBDS-IS 8.0.2 Install Guide: Implement installation information > --------------------------------------------------------------- > > Key: TOOLSDOC-658 > URL: https://issues.jboss.org/browse/TOOLSDOC-658 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > > [1] - > > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio_Integration_Stack/8.0/html/Install_Red_Hat_JBoss_Developer_Studio_Integration_Stack/index.html > I really find these instructions waay to complicated and since > everything is on the same level they all look equally important. > They also don't actually use the fastest way for marketplace. > Here is what I would focus on: > 1. Install into existing Eclipse: > Use > http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-integration-stack-luna > Link to #2 about Early access > 2. Install into existing JBoss Developer Studio > Use JBoss Central > Explain additional features available under Early access > 3. Other > Install/uninstall additional features from JBoss Central > Install offline: the instructions should not be different for > eclipse or devstudio. > (section 9 could be here but I would just not worry about > documenting it) > That's it. > This makes it much less complicated IMO. > Can we make that happen ? > /max -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:47:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-648) JBDS-IS: Update the Install guide with info for installing JBDS IS in Eclipse when Offline In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Ali updated TOOLSDOC-648: ------------------------------- Sprint: 06-Jul >> 19-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 09-Nov >> 22-Nov 2015-JBDS/JBT (was: 06-Jul >> 19-Jul 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 14-Sep >> 27-Sep 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT) > JBDS-IS: Update the Install guide with info for installing JBDS IS in Eclipse when Offline > ------------------------------------------------------------------------------------------ > > Key: TOOLSDOC-648 > URL: https://issues.jboss.org/browse/TOOLSDOC-648 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.3.0.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > Change the info in the install JBDS IS in Eclipse when Offline section to two .zips instead of three .zips required for installing. This will change in the next version of JBDS IS that is based on JBDS 9.0.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:47:00 2015 From: issues at jboss.org (Misha Ali (JIRA)) Date: Sun, 25 Oct 2015 22:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-689) JBDS-IS 8.0.4: Release Notes In-Reply-To: References: Message-ID: Misha Ali created TOOLSDOC-689: ---------------------------------- Summary: JBDS-IS 8.0.4: Release Notes Key: TOOLSDOC-689 URL: https://issues.jboss.org/browse/TOOLSDOC-689 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:51:00 2015 From: issues at jboss.org (Yogesh Naravane (JIRA)) Date: Sun, 25 Oct 2015 22:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-528) blueprint validation error after converting fuse project to jpa In-Reply-To: References: Message-ID: Yogesh Naravane created JBTIS-528: ------------------------------------- Summary: blueprint validation error after converting fuse project to jpa Key: JBTIS-528 URL: https://issues.jboss.org/browse/JBTIS-528 Project: JBoss Tools Integration Stack Issue Type: Bug Components: Fuse IDE Environment: jbds 810 GA, integration tooling for fuse [7.3.1.v20150810-1602-H64-Final] Reporter: Yogesh Naravane Priority: Minor Attachments: eclipseError.png converting defautl blueprint fuse project to jpa project shows validation error. due to missing jpa namespace expected behaviour: jbds should re-write blueprint.xml to provide necessary namespaces. OR What is preferred way to write missing namespace. i.e. xmlns:jpa="http://aries.apache.org/xmlns/jpan/v1.0.0" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:57:00 2015 From: issues at jboss.org (Yogesh Naravane (JIRA)) Date: Sun, 25 Oct 2015 22:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-528) blueprint validation error after converting fuse project to jpa In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogesh Naravane updated JBTIS-528: ---------------------------------- Description: converting default blueprint fuse project to jpa project shows validation error. due to missing jpa namespace expected behavior: jbds should re-write blueprint.xml to provide necessary namespaces. OR What is preferred way to write missing namespace. i.e. xmlns:jpa="http://aries.apache.org/xmlns/jpan/v1.0.0" was: converting defautl blueprint fuse project to jpa project shows validation error. due to missing jpa namespace expected behaviour: jbds should re-write blueprint.xml to provide necessary namespaces. OR What is preferred way to write missing namespace. i.e. xmlns:jpa="http://aries.apache.org/xmlns/jpan/v1.0.0" > blueprint validation error after converting fuse project to jpa > --------------------------------------------------------------- > > Key: JBTIS-528 > URL: https://issues.jboss.org/browse/JBTIS-528 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Environment: jbds 810 GA, integration tooling for fuse [7.3.1.v20150810-1602-H64-Final] > Reporter: Yogesh Naravane > Priority: Minor > Attachments: eclipseError.png > > > converting default blueprint fuse project to jpa project shows validation error. > due to missing jpa namespace > expected behavior: jbds should re-write blueprint.xml to provide necessary > namespaces. OR > What is preferred way to write missing namespace. i.e. > xmlns:jpa="http://aries.apache.org/xmlns/jpan/v1.0.0" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 25 22:58:00 2015 From: issues at jboss.org (Yogesh Naravane (JIRA)) Date: Sun, 25 Oct 2015 22:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-528) blueprint validation error after converting fuse project to jpa In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogesh Naravane updated JBTIS-528: ---------------------------------- Workaround Description: After conversion blueprint expects namespace related to jpa but its missing. i.e. xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.1.0" After adding it manually the error vanishes. was: After conversion blueprint expects namespace realted to jpa but its missing. i.e. xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.1.0" After adding it manually the error vanishes. > blueprint validation error after converting fuse project to jpa > --------------------------------------------------------------- > > Key: JBTIS-528 > URL: https://issues.jboss.org/browse/JBTIS-528 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Environment: jbds 810 GA, integration tooling for fuse [7.3.1.v20150810-1602-H64-Final] > Reporter: Yogesh Naravane > Priority: Minor > Attachments: eclipseError.png > > > converting default blueprint fuse project to jpa project shows validation error. > due to missing jpa namespace > expected behavior: jbds should re-write blueprint.xml to provide necessary > namespaces. OR > What is preferred way to write missing namespace. i.e. > xmlns:jpa="http://aries.apache.org/xmlns/jpan/v1.0.0" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 04:30:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Mon, 26 Oct 2015 04:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 04:30:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 04:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: Mickael Istria created JBDS-3553: ------------------------------------ Summary: Integrate/Enable CodeRecommenders substring completion in JBDS Key: JBDS-3553 URL: https://issues.jboss.org/browse/JBDS-3553 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: p2-product Reporter: Mickael Istria Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 05:16:00 2015 From: issues at jboss.org (David Hladky (JIRA)) Date: Mon, 26 Oct 2015 05:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121842#comment-13121842 ] David Hladky commented on JBDS-3547: ------------------------------------ It was not always there. The Eloqua tracking was added in February 2014 as an optional feature (the one adding the product downloads was able set Eloqua tracking on per product base). From what I remember the Eloqua tracking was added to all product downloads. > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 05:23:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 26 Oct 2015 05:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121456#comment-13121456 ] Supriya Bharadwaj edited comment on TOOLSDOC-307 at 10/26/15 5:22 AM: ---------------------------------------------------------------------- > Checked where can the info be added in the existing artilces for OS2 > Decided on > https://access.redhat.com/articles/1295883#republishmodifiedapp > Add a note or another sentence in the task (and not in the DYK section since the info will be easily spotted in the task) > Tried the same steps on OS3 to confirm if the addition must be made in OS3 docs too was (Author: supriya.bharadwaj): > Chaecked where can the info be added in the existing artilces for OS2 > Decided on > https://access.redhat.com/articles/1295883#republishmodifiedapp > Add a note or another sentence in the task (and not in the DYK section since the info will be easily spotted in the task) > Tried the same steps on OS3 to confirm if the addition must be made in OS3 docs too > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 08:12:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 26 Oct 2015 08:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121902#comment-13121902 ] Supriya Bharadwaj commented on TOOLSDOC-307: -------------------------------------------- > Added the info in the portal version of the doc at: https://access.redhat.com/node/1295883/draft#republishmodifiedapp in section 3 step 1. > Added info in the community doc > Requested Misha to create a PR > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 08:13:00 2015 From: issues at jboss.org (Supriya Bharadwaj (JIRA)) Date: Mon, 26 Oct 2015 08:13:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supriya Bharadwaj updated TOOLSDOC-307: --------------------------------------- Attachment: openshift_importapp.adoc Hi [~mhusnain], can you please create a PR for this? Thanks - supriya > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Beta1 > > Attachments: openshift_importapp.adoc > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1.html > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha1.html > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 08:21:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 26 Oct 2015 08:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121907#comment-13121907 ] Max Rydahl Andersen commented on JBIDE-20845: --------------------------------------------- How can disable the warning make what Martin see works ? His issue is not that the warning is shown, it is that even when saying ok to the warning the breakpoint is still not hit. > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 08:55:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 08:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121924#comment-13121924 ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- {quote}The video don't show what happens if I disable earlyaccess - will I still be proposed earlyaccess content when installing ?{quote} Yes, you get asked about Early-Access or not whenever you have choice between 2 "flavours" of the same connector, independently of whether Early-Access sites are enabled or not. {quote}Also how does it handle when there is a "non-installable connector" vs "earlyaccess connector" ? {quote} I need to check this scenario. I'm not sure it's correctly handled with suggested implementation. What do you think is user expectation in that case? {quote}Suggestion: don't force users to see the detailed earlyaccess info just to turn it off. Have a checkbox with "Show earlyaccess" and earlyaccess underlined. Have it on by default (opposite to what we had until now), clicking earlyaccess get you to the detailed dialog for more info and unchecking the checkbox = disable earlyaccess and after that EA won't be suggested to install. WDYT ?{quote} Can you give details about the "turn if off" ? For this installation process, it can mean several things (hide EA connectors and/or remove EA sites). The benefit of the dialog is that is comes with some clearer explanation of the action user can perform on EA. With my proposed change change, instead of dealing with filtering in the viewer, user is facing the choice of regular vs EA in a pop-up only when it makes sense for them. What you suggest seems to remove this popup and to stick with a concept of early-access "state" in the viewer which I believe is not necessary at that time and is more complex than asking the question to user as part of the installation process. Also, I do not see a reason for hiding Early-Access content when there is no "regular" one. {quote}On video EA connector installed, but after restart it looks like normal connector was installed not EA.{quote} It's because in that example, the normal connector is a subset of EA connector. So installing content of EA installs the content of normal and the discovery mechanism assumes that both are installed. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 08:59:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 08:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121926#comment-13121926 ] Nick Boldt commented on JBDS-3547: ---------------------------------- Does this change apply to ALL download links, including those referring to content published before Feb 2014? Or just the newer ones? > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 09:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 26 Oct 2015 09:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3553: --------------------------------- Fix Version/s: 9.0.1.Beta1 > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 09:40:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 26 Oct 2015 09:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3553: ------------------------------------ Assignee: Mickael Istria Agreed. We should enable it in JBDS. [~mickael_istria] could you take care of it? > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 09:45:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 26 Oct 2015 09:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-527: -------------------------------- Assignee: Paul Leacu > com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-527 > URL: https://issues.jboss.org/browse/JBTIS-527 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > > Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.Alpha2.jbds-is/earlyaccess/ I see these 4 IUs: > {code} > com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 > {code} > They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: > * 9.0.0.Alpha2-v20151006-2058-B148 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 09:45:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 26 Oct 2015 09:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-526) JBDSIS on marketplace contains category for WTP patches In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-526: -------------------------------- Assignee: Paul Leacu > JBDSIS on marketplace contains category for WTP patches > ------------------------------------------------------- > > Key: JBTIS-526 > URL: https://issues.jboss.org/browse/JBTIS-526 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.3.GA > Environment: Eclipse Luna JEE SR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis803_marketplace_features.png > > > JBDSIS on marketplace contains category for WTP patches. Is this really intended (see the attached screenshot)? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 10:07:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3518) Eclipse-cs update to 6.9.0 on JBoss Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria reassigned JBDS-3518: ------------------------------------ Assignee: Nick Boldt (was: Mickael Istria) > Eclipse-cs update to 6.9.0 on JBoss Central > ------------------------------------------- > > Key: JBDS-3518 > URL: https://issues.jboss.org/browse/JBDS-3518 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: 3rd-party-certification, build, central > Affects Versions: 9.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 9.0.1.Beta1 > > Attachments: checkstyle.png > > > I've checked Release 6.9.0 with JBDS 9.0.0.CR1 and experienced no issues. > Changes since last version: http://eclipse-cs.sourceforge.net/#!/releasenotes -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 10:09:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 10:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3518) Eclipse-cs update to 6.9.0 on JBoss Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121958#comment-13121958 ] Mickael Istria commented on JBDS-3518: -------------------------------------- Assigning to [~nickboldt] since he was much more active in this discussion so I believe he's the best one to take care of that change, but feel free to reassign to me if you want that I specifically apply the necessary changes. > Eclipse-cs update to 6.9.0 on JBoss Central > ------------------------------------------- > > Key: JBDS-3518 > URL: https://issues.jboss.org/browse/JBDS-3518 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: 3rd-party-certification, build, central > Affects Versions: 9.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 9.0.1.Beta1 > > Attachments: checkstyle.png > > > I've checked Release 6.9.0 with JBDS 9.0.0.CR1 and experienced no issues. > Changes since last version: http://eclipse-cs.sourceforge.net/#!/releasenotes -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 10:19:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Mon, 26 Oct 2015 10:19:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121963#comment-13121963 ] Fred Bricon commented on JBDS-3553: ----------------------------------- +1 > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 10:22:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Mon, 26 Oct 2015 10:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121965#comment-13121965 ] Len DiMaggio commented on JBDS-3553: ------------------------------------ +1 too! > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:14:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 11:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121996#comment-13121996 ] Nick Boldt commented on JBIDE-21012: ------------------------------------ That's true in theory as of this moment, it's currently impossible. We need a way to ensure that there's an unpacked update site in nexus, such as: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ Currently that folder exists but is empty. Once it has content, we can start using it in parent pom [0] and composite*.xml [1] in place of what's currently there. [0] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L102 [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/_composite_/core/master/compositeArtifacts.xml Perhaps we need to add a *build-helper-maven-plugin::package::attach-artifact* build step to each update site pom, as we do for Locus [2]? [2] https://github.com/jbosstools/jbosstools-locus/blob/master/deployment/pom.xml#L35 Or for the sake of reuse, perhaps it's better in the parent pom. We could add it to the existing deploy-to-jboss.org profile, or create a new *deploy-to-nexus-unzip* profile? [~mickael_istria] WDYT? > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:31:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 11:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122006#comment-13122006 ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- The reasons why this was experimentally implemented are in JBIDE-16128 . However, it's now pretty clear that we're not able/not willing to bump Maven artifacts versions between milestones, so it makes that we're not able to use Nexus in our build pipeline. I wouldn't mind if we remove the deploy step from CI jobs. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:37:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 11:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122012#comment-13122012 ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- The issue noticed by [~nickboldt] about empty folders on Nexus is a relatively new one. I'm positive on the fact that when the profile was introduced, the zips were attached on Nexus, and the sites were available. Maybe something changed in our conventions or in Tycho to explain the new behaviour. In any case, as I mentioned above, as long as we keep same Maven version in pom.xml for a year, and for both branch and master, we cannot rely on Nexus for our builds. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:38:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 11:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122012#comment-13122012 ] Mickael Istria edited comment on JBIDE-21012 at 10/26/15 11:37 AM: ------------------------------------------------------------------- The issue noticed by [~nickboldt] about empty folders on Nexus is a relatively new one. I'm positive on the fact that when the profile was introduced, the zips were attached on Nexus, and the sites were available. Maybe something changed in our conventions or in Tycho to explain the new behaviour. In any case, as I mentioned above, as long as we keep same Maven version in pom.xml for a year, and for both branch and master, we cannot rely on Nexus for our builds/publishing of snapshot component sites. was (Author: mickael_istria): The issue noticed by [~nickboldt] about empty folders on Nexus is a relatively new one. I'm positive on the fact that when the profile was introduced, the zips were attached on Nexus, and the sites were available. Maybe something changed in our conventions or in Tycho to explain the new behaviour. In any case, as I mentioned above, as long as we keep same Maven version in pom.xml for a year, and for both branch and master, we cannot rely on Nexus for our builds. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:46:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 26 Oct 2015 11:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122018#comment-13122018 ] Max Rydahl Andersen commented on JBIDE-21012: --------------------------------------------- wether we use nexus or not we can't keep the same maven version in pom.xml for a year both branch and master. So if we do that then we got a problem. Which pom.xml are you explicitly referring to here? > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:55:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 26 Oct 2015 11:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122022#comment-13122022 ] Max Rydahl Andersen commented on JBDS-3553: ------------------------------------------- to be clear - I'm +1 on adding coderecommenders in, but lets just do some basic due diligence. substring completion is just one of many, right? Can someone outline the features we get beyond it ? last I checked the big feature of code recommenders was about showing the % of the likelihood of a completion being relevant for a given situation - afaik that only works for SWT/Eclipse platform code. Not for Java/JavaEE in general. Can anyone confirm ? The coderecommenders rely on a remote DB to be updated and I believe thre might also be data sent to coderecommenders or eclipse - is that part of the default code recommender suggested here ? if yes, how does that affect our online/offline story (if at all) ? > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:56:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 11:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122023#comment-13122023 ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- The version in pom.xml at the root of each component and in children pom are not changed between milestones. They are changed yearly. We only change the version of the parent pom, but this doesn't cascade to update sites pom. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 12:05:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 26 Oct 2015 12:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122029#comment-13122029 ] Max Rydahl Andersen commented on JBIDE-21012: --------------------------------------------- so the updatesite pom don't pick up the alpha/beta/etc. qualifier ? any ways it could do that ? or is the solution that before release we set the site pom to have the right qualifier ? > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 12:12:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 12:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122033#comment-13122033 ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- AFAIK, setting the value before release seems best. See JBIDE-16128 for more details. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 12:33:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 26 Oct 2015 12:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-21022: ------------------------------------------- Summary: open of .md files in project examples don't use markdown editor Key: JBIDE-21022 URL: https://issues.jboss.org/browse/JBIDE-21022 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Reporter: Max Rydahl Andersen even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 12:49:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Mon, 26 Oct 2015 12:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122053#comment-13122053 ] Snjezana Peco commented on JBIDE-20845: --------------------------------------- I can't reproduce the issue on Windows and Linux. {quote} But for Vlado (Fedora 22, KDE) it worked right away - no Line Number error and no need to click any button in the web app {quote} If the "Wa&rn when unable to install breakpoint due to missing line number attributes" property is unchecked, it will work as described above. If the property is checked, we will get the Java Breakpoint dialog, but the breakpoint will be hit without clicking any buttons. {quote} This cannot be right. removing the warning won't actually fix this issue of the breakpoint not being hit. And we should not be hardwiring user preferences in our setup like this IMO. {quote} I have thought you want to disable the Java Breakpoint dialog by default. [~mmalina] can you reproduce the issue when the "Wa&rn when unable to install breakpoint due to missing line number attributes" property is unchecked? > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 12:59:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 26 Oct 2015 12:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122056#comment-13122056 ] Paul Leacu commented on JBTIS-508: ---------------------------------- Corrected JBTIS composites: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/d65979fb916de09e6c030770e6890ca31c07e485 > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 13:45:01 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Mon, 26 Oct 2015 13:45:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122068#comment-13122068 ] Andre Dietisheim commented on JBIDE-20764: ------------------------------------------ In a 1st batch we'll try to implement "oc rsync" for incremental deployment. The [PR|https://github.com/openshift/origin/pull/4787] for "oc rsync" unveils the details of the implementation. It's using rsync if the client OS is linux, *tar* on windows. An exemplary usage can be read here: https://github.com/openshift/origin/blob/master/docs/generated/oc_by_example_content.adoc#oc-rsync > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: server adapter wizard.bmml, server adapter wizard.png > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 13:57:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 13:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122074#comment-13122074 ] Nick Boldt commented on JBTIS-508: ---------------------------------- Looks good! Did you also want to merge your content into the JBT 4.3.0.Final composite sites, so we have simpler URLs in ide-config.properties and fewer URLs showing up in Eclipse? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 14:02:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 14:02:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122075#comment-13122075 ] Nick Boldt commented on JBIDE-21012: ------------------------------------ Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master >=308 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 14:03:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 14:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122075#comment-13122075 ] Nick Boldt edited comment on JBIDE-21012 at 10/26/15 2:02 PM: -------------------------------------------------------------- Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Run locally: {code} mvn clean install -DBUILD_NUMBER=1234 && ll site/target/*.zip site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_* [INFO] freemarker.site .................................... SUCCESS [ 4.587 s] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ {code} Results: * site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_1.5.100.Alpha1-v20151026-1703-B1234.jar * site/target/freemarker.site-1.5.100.Alpha1-v20151026-1703-B1234.zip Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master >=308 was (Author: nickboldt): Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master >=308 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 14:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122075#comment-13122075 ] Nick Boldt edited comment on JBIDE-21012 at 10/26/15 2:03 PM: -------------------------------------------------------------- Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Run locally: {code} mvn clean install -DBUILD_NUMBER=1234 && ll site/target/*.zip site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_* {code} Results: * site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_1.5.100.Alpha1-v20151026-1703-B1234.jar * site/target/freemarker.site-1.5.100.Alpha1-v20151026-1703-B1234.zip Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master >=308 was (Author: nickboldt): Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Run locally: {code} mvn clean install -DBUILD_NUMBER=1234 && ll site/target/*.zip site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_* [INFO] freemarker.site .................................... SUCCESS [ 4.587 s] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ {code} Results: * site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_1.5.100.Alpha1-v20151026-1703-B1234.jar * site/target/freemarker.site-1.5.100.Alpha1-v20151026-1703-B1234.zip Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master >=308 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 14:08:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Mon, 26 Oct 2015 14:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-21022: ----------------------------------- Assignee: Snjezana Peco > open of .md files in project examples don't use markdown editor > --------------------------------------------------------------- > > Key: JBIDE-21022 > URL: https://issues.jboss.org/browse/JBIDE-21022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > > even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 14:51:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 14:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122091#comment-13122091 ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- The issue I foresee with this approach is that there will not be a predictable URL for that zip, or the URL would still be the same, without the BUILD_ALIAS, still colliding in case we have same Maven versions on multiple branches. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 14:59:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 14:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122094#comment-13122094 ] Nick Boldt commented on JBIDE-21012: ------------------------------------ So the last time that we had successfully deployed to Nexus and the unzip plugin fired to create the unpacked site was on *Thu Nov 13 09:33:23 EST 2014* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.4.0-SNAPSHOT/freemarker.site-1.4.0-SNAPSHOT.zip-unzip/ Not sure why deployment continues but unzipping does not. --- Found a way to push to Nexus snapshots using a classifier to define the BUILD_ALIAS... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_master/310/console http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_master/ws/sources/site/target/freemarker.site-1.5.100-SNAPSHOT.zip ends up with: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151026.184902-11-Alpha1-v20151026-1848-B310.zip instead of https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151013.204143-6.zip However, there's nothing in the unzip area: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 15:23:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Mon, 26 Oct 2015 15:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122097#comment-13122097 ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- I see that unzip area for all our recent builds seem empty. Since the zip gets to Nexus, it's not a Tycho issue, but a Nexus one. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:03:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 26 Oct 2015 16:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122113#comment-13122113 ] Alexey Kazakov commented on JBDS-3553: -------------------------------------- > substring completion is just one of many, right? > Can someone outline the features we get beyond it ? Yes. There are: - % of most used calls for: Call Completion, Constructor Completion, Override Completion - Subtypes Completion (disabled by default) - Subwords Completion - Chain Completion (e.g. getA().foo().setB().doSomeOtherStuff() etc.) - Adaptive Template Completion (inserts group of methods) - Mylyn Completion The full list of features is here: https://www.eclipse.org/recommenders/manual/ > last I checked the big feature of code recommenders was about showing the % of the likelihood of a completion being relevant for a given situation - afaik that only works for SWT/Eclipse platform code. Not for Java/JavaEE in general. Can anyone confirm ? That's true. Afaik you have to provide your own remote model if you want to extend it. For example Mars by default includes http://download.eclipse.org/recommenders/models/mars only. It's mostly about SWT stuff only. > The coderecommenders rely on a remote DB to be updated and I believe thre might also be data sent to coderecommenders or eclipse - is that part of the default code recommender suggested here ? if yes, how does that affect our online/offline story (if at all) ? Afaik Eclipse downloads the models listed in the model repositories view. So you probably should be online to download them. Don't know if you can pre-download them and include in the installation and use them as a cache. > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:12:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 16:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122115#comment-13122115 ] Nick Boldt commented on JBIDE-21012: ------------------------------------ I was halfway through sending an email to ci-issues@ to report that the unzip process wasn't working, when suddenly this appeared: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1-v20151026-1848-B310.zip-unzip/ But when I look elsewhere (in another browser) this is still empty: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ So... if I just use the BUILD_ALIAS we can have reusable URLs for all of a given branch (for any given BUILD_ALIAS & project.version combination). So, I did that... updated the PR, and kicked a fresh build B311. Results: * *{color:green}This now exists:{color}* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1.zip-unzip/ * *{color:red}This has vanished / is 404'd:{color}* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1-v20151026-1848-B310.zip-unzip/ HOWEVER... seems there's about a 20 min lag between the Jenkins job and the unzip URL appearing. So... we can use this approach, but it's a bit slower than the lag on download.jboss.org. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:26:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Mon, 26 Oct 2015 16:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122119#comment-13122119 ] Paul Leacu commented on JBTIS-508: ---------------------------------- Corrected JBDSIS composites: https://github.com/jbdevstudio/jbdevstudio-website/commit/5895d812df4917633d2da5976a5f280df5653ce5 I guess I don't know if I want to hide the JBTIS composite site in the parent JBT 4.3.0.Final. It might be more useful to stand out since it's Alpha2. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:27:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 16:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21012: ------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:27:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 16:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21012: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-freemarker/pull/54, https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 (was: https://github.com/jbdevstudio/jbdevstudio-ci/pull/156) > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:35:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 16:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122122#comment-13122122 ] Nick Boldt commented on JBIDE-21012: ------------------------------------ So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/${project.name}-${project.version}.zip into the Nexus deployment. 3. set ${BUILD_ALIAS} if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:35:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 16:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122122#comment-13122122 ] Nick Boldt edited comment on JBIDE-21012 at 10/26/15 4:34 PM: -------------------------------------------------------------- So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/\${project.name}-\${project.version}.zip into the Nexus deployment. 3. set ${BUILD_ALIAS} if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. was (Author: nickboldt): So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/${project.name}-${project.version}.zip into the Nexus deployment. 3. set ${BUILD_ALIAS} if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 16:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122122#comment-13122122 ] Nick Boldt edited comment on JBIDE-21012 at 10/26/15 4:35 PM: -------------------------------------------------------------- So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/$\{project.name}-$\{project.version}.zip into the Nexus deployment. 3. set ${BUILD_ALIAS} if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. was (Author: nickboldt): So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/\${project.name}-\${project.version}.zip into the Nexus deployment. 3. set ${BUILD_ALIAS} if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 16:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122122#comment-13122122 ] Nick Boldt edited comment on JBIDE-21012 at 10/26/15 4:35 PM: -------------------------------------------------------------- So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/$\{project.name}-$\{project.version}.zip into the Nexus deployment. 3. set $\{BUILD_ALIAS} if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. was (Author: nickboldt): So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/$\{project.name}-$\{project.version}.zip into the Nexus deployment. 3. set ${BUILD_ALIAS} if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/ I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 16:47:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Mon, 26 Oct 2015 16:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snjezana Peco reassigned JBIDE-21022: ------------------------------------- Assignee: Fred Bricon (was: Snjezana Peco) Could you, please, review the PR? > open of .md files in project examples don't use markdown editor > --------------------------------------------------------------- > > Key: JBIDE-21022 > URL: https://issues.jboss.org/browse/JBIDE-21022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > > even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 17:06:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Mon, 26 Oct 2015 17:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122135#comment-13122135 ] Nick Boldt commented on JBTIS-508: ---------------------------------- Illogical. You hid the JBDS IS 9 Alpha2 ones [1] [2]; why not also hide the JBT IS 4.3 Alpha2 ones [3], [4] ? [1] https://devstudio.redhat.com/9.0/stable/updates/compositeContent.xml [2] https://devstudio.redhat.com/9.0/stable/updates/earlyaccess/compositeContent.xml [3] http://download.jboss.org/jbosstools/mars/stable/updates/compositeContent.xml [4] http://download.jboss.org/jbosstools/mars/stable/updates/earlyaccess/compositeContent.xml > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 17:45:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 26 Oct 2015 17:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBTIS-529: ----------------------------------------- Summary: fuse fails to install from jboss central Key: JBTIS-529 URL: https://issues.jboss.org/browse/JBTIS-529 Project: JBoss Tools Integration Stack Issue Type: Bug Reporter: Max Rydahl Andersen Priority: Blocker not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. But even with or without earlyaccess installing via the wizard result in: Problems occurred while performing installation: There are no connectors to install There are no connectors to install /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 17:57:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 26 Oct 2015 17:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122142#comment-13122142 ] Alexey Kazakov commented on JBTIS-529: -------------------------------------- cc: [~nickboldt], [~mickael_istria], [~pleacu] > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Priority: Blocker > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 18:35:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Mon, 26 Oct 2015 18:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122153#comment-13122153 ] Fred Bricon commented on JBTIS-529: ----------------------------------- So there are actually several problems here - fuse wizard/quickstarts show up even if EA is disabled: caused by only checking if IS update site is available, ignoring the EA flag. We can fix that server side - no connectors found when selecting the wizard: somehow the jboss.integration-stack.ea.bundle.fuse connector is not loaded apparently. I don't know why yet, need more investigation. Could be a problem either in JBT or JBTIS. - all fuse quickstarts show as having the fuse tooling installed when it's not. This is caused by an unfortunate hard coded id in https://github.com/jbosstools/jbosstools-central/blob/master/examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/internal/model/RequirementModelUtil.java#L174. Ideally the whole requirement inference logic should be externalized, but the logic is not trivial, so it's a bit tricky. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Priority: Blocker > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 21:45:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Mon, 26 Oct 2015 21:45:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21023) ctrl+shft+G sometimes give NPE in cdi tooling In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-21023: ------------------------------------------- Summary: ctrl+shft+G sometimes give NPE in cdi tooling Key: JBIDE-21023 URL: https://issues.jboss.org/browse/JBIDE-21023 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Reporter: Max Rydahl Andersen used Ctrl+Shift+G on MemberService.java:@Inject validator from html5 kitchensink gave me: {code} java.lang.NullPointerException at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.containsInSearchScope(InjectionPointQueryParticipant.java:69) at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.search(InjectionPointQueryParticipant.java:104) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170) at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 21:49:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 26 Oct 2015 21:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21023) ctrl+shft+G sometimes give NPE in cdi tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21023: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > ctrl+shft+G sometimes give NPE in cdi tooling > --------------------------------------------- > > Key: JBIDE-21023 > URL: https://issues.jboss.org/browse/JBIDE-21023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > used Ctrl+Shift+G on MemberService.java:@Inject validator from html5 kitchensink > gave me: > {code} > java.lang.NullPointerException > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.containsInSearchScope(InjectionPointQueryParticipant.java:69) > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.search(InjectionPointQueryParticipant.java:104) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170) > at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 21:50:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Mon, 26 Oct 2015 21:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21023) ctrl+shft+G sometimes give NPE in cdi tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBIDE-21023: -------------------------------------- Assignee: Daniel Azarov > ctrl+shft+G sometimes give NPE in cdi tooling > --------------------------------------------- > > Key: JBIDE-21023 > URL: https://issues.jboss.org/browse/JBIDE-21023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > used Ctrl+Shift+G on MemberService.java:@Inject validator from html5 kitchensink > gave me: > {code} > java.lang.NullPointerException > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.containsInSearchScope(InjectionPointQueryParticipant.java:69) > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.search(InjectionPointQueryParticipant.java:104) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170) > at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 00:26:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 27 Oct 2015 00:26:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21024) webservice tester "forgets" parameterized url In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-21024: ------------------------------------------- Summary: webservice tester "forgets" parameterized url Key: JBIDE-21024 URL: https://issues.jboss.org/browse/JBIDE-21024 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Reporter: Max Rydahl Andersen use html5 kitchensink example and one of the urls you can run is "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/{id:[0-9][0-9]*}" When you run this webservice tester will ask you about id - great. But when executing the first time it will reset the url to "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/" meaning it is not possible to run again without manually typing it in. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 01:58:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Tue, 27 Oct 2015 01:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21025) hibernate querying nor content assist is broken In-Reply-To: References: Message-ID: Max Rydahl Andersen created JBIDE-21025: ------------------------------------------- Summary: hibernate querying nor content assist is broken Key: JBIDE-21025 URL: https://issues.jboss.org/browse/JBIDE-21025 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Reporter: Max Rydahl Andersen Priority: Blocker using html5-kitchensink I cannot get basic content assist to work. "from Member m where m.|" gives no content assist at all. And trying to run the query results in: {code} java.lang.NullPointerException at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1888) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845) at org.jboss.tools.hibernate.runtime.v_4_3.internal.ConfigurationFacadeImpl.buildTargetSessionFactory(ConfigurationFacadeImpl.java:24) at org.jboss.tools.hibernate.runtime.common.AbstractConfigurationFacade.buildSessionFactory(AbstractConfigurationFacade.java:169) at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108) at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) 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:1499) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) 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:483) 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) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 06:05:49 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Tue, 27 Oct 2015 06:05:49 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122271#comment-13122271 ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- That seems interesting! Did you try to deploy the same site with different BUILD_ALIAS to see whether both remain available on Nexus or if one would discard the other? > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 08:56:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 27 Oct 2015 08:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu reassigned JBTIS-529: -------------------------------- Assignee: Fred Bricon > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 08:58:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 27 Oct 2015 08:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122417#comment-13122417 ] Paul Leacu commented on JBTIS-529: ---------------------------------- [~fbricon] - Looks like you're ahead of the pack in investigating this - assigning to you initially, > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 09:05:00 2015 From: issues at jboss.org (David Hladky (JIRA)) Date: Tue, 27 Oct 2015 09:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122427#comment-13122427 ] David Hladky commented on JBDS-3547: ------------------------------------ Every link, that goes to www.jboss.org/download-manager/.... is tracked in Download manager. This means old downloads as well. The reason is you can add the link to the file anywhere including 3rd party forums and the downloads are tracked. > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 09:08:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 09:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21025) hibernate querying nor content assist is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers reassigned JBIDE-21025: --------------------------------- Assignee: Koen Aers > hibernate querying nor content assist is broken > ----------------------------------------------- > > Key: JBIDE-21025 > URL: https://issues.jboss.org/browse/JBIDE-21025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > > using html5-kitchensink I cannot get basic content assist to work. > "from Member m where m.|" gives no content assist at all. > And trying to run the query results in: > {code} > java.lang.NullPointerException > at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1888) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845) > at org.jboss.tools.hibernate.runtime.v_4_3.internal.ConfigurationFacadeImpl.buildTargetSessionFactory(ConfigurationFacadeImpl.java:24) > at org.jboss.tools.hibernate.runtime.common.AbstractConfigurationFacade.buildSessionFactory(AbstractConfigurationFacade.java:169) > at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108) > at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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:483) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 09:33:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 27 Oct 2015 09:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21024) webservice tester "forgets" parameterized url In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-21024: ----------------------------------- Assignee: Xavier Coulon > webservice tester "forgets" parameterized url > --------------------------------------------- > > Key: JBIDE-21024 > URL: https://issues.jboss.org/browse/JBIDE-21024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > use html5 kitchensink example and one of the urls you can run is "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/{id:[0-9][0-9]*}" > When you run this webservice tester will ask you about id - great. > But when executing the first time it will reset the url to "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/" meaning it is not possible to run again without manually typing it in. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:11:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 27 Oct 2015 10:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122483#comment-13122483 ] Paul Leacu commented on JBTIS-508: ---------------------------------- Agreed - consistency demands merged IS composites: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/aac2cde32e1a8d5c44af2b9bc2001d576804d319 > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:18:00 2015 From: issues at jboss.org (Andre Dietisheim (JIRA)) Date: Tue, 27 Oct 2015 10:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122068#comment-13122068 ] Andre Dietisheim edited comment on JBIDE-20764 at 10/27/15 10:17 AM: --------------------------------------------------------------------- In a 1st batch we'll try to implement "oc rsync" for incremental deployment. The [PR|https://github.com/openshift/origin/pull/4787] for "oc rsync" unveils the details of the implementation. It's using rsync if the client OS is linux, *tar* on windows. An additonal [PR|https://github.com/openshift/origin/pull/5351] replaces *tar* with *rsync* on windows. For windows users would then be required to install cygwin or rsync from https://www.itefix.net/cwrsync An exemplary usage can be read here: https://github.com/openshift/origin/blob/master/docs/generated/oc_by_example_content.adoc#oc-rsync was (Author: adietish): In a 1st batch we'll try to implement "oc rsync" for incremental deployment. The [PR|https://github.com/openshift/origin/pull/4787] for "oc rsync" unveils the details of the implementation. It's using rsync if the client OS is linux, *tar* on windows. An exemplary usage can be read here: https://github.com/openshift/origin/blob/master/docs/generated/oc_by_example_content.adoc#oc-rsync > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: server adapter wizard.bmml, server adapter wizard.png > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:52:03 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 10:52:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122513#comment-13122513 ] Nick Boldt commented on JBTIS-508: ---------------------------------- Since this is ALSO the latest content for the JBT & JBDS development sites (the latest stable milestone = 9.0.0.GA / 4.3.0.Final = latest release too) should you not also update these four /development/ URLs too? [1] https://devstudio.redhat.com/9.0/development/updates/ composite*.xml [2] https://devstudio.redhat.com/9.0/development/updates/earlyaccess/ composite*.xml [3] http://download.jboss.org/jbosstools/mars/development/updates/ composite*.xml [4] http://download.jboss.org/jbosstools/mars/development/updates/earlyaccess/ composite*.xml Are all these manual changes reflected in your updated release guide, so that you'll update BOTH stable and development as appropriate when you release your next Alpha or Beta bits? Can you link to that document here? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:55:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 10:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers updated JBIDE-20801: ------------------------------ Fix Version/s: 4.4.0.Alpha1 > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:56:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 10:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: Koen Aers created JBIDE-21026: --------------------------------- Summary: New hibernate configuration wizard controls invisible in Unix Key: JBIDE-21026 URL: https://issues.jboss.org/browse/JBIDE-21026 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.3.0.CR1 Reporter: Dmitry Bocharov Assignee: Koen Aers Priority: Minor Fix For: 4.4.0.Alpha1 Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:57:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 10:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers updated JBIDE-21026: ------------------------------ Fix Version/s: 4.3.1.Beta1 (was: 4.4.0.Alpha1) > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-21026 > URL: https://issues.jboss.org/browse/JBIDE-21026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.3.1.Beta1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:57:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 10:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers resolved JBIDE-21026. ------------------------------- Resolution: Done > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-21026 > URL: https://issues.jboss.org/browse/JBIDE-21026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.3.1.Beta1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 10:57:01 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 10:57:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers resolved JBIDE-20801. ------------------------------- Resolution: Done > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 11:20:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 27 Oct 2015 11:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled) In-Reply-To: References: Message-ID: Alexey Kazakov created JBIDE-21027: -------------------------------------- Summary: Central offers to install Early Access content when importing project examples (EA disabled) Key: JBIDE-21027 URL: https://issues.jboss.org/browse/JBIDE-21027 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, project-examples Affects Versions: 4.3.0.Final Reporter: Alexey Kazakov Assignee: Mickael Istria Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 Attachments: angular.png 1. Open Central with EA disabled 2. Try to import kitchensink-angularjs project example 3. AngularJS (EA version) is offered to install: !angular.png! 4. Press "Download & Install". 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 11:22:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 27 Oct 2015 11:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122541#comment-13122541 ] Alexey Kazakov commented on JBIDE-21027: ---------------------------------------- Assigning to [~mickael_istria] because it should be aligned with JBIDE-20609 > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 11:37:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Tue, 27 Oct 2015 11:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-488) JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122558#comment-13122558 ] Paul Leacu commented on JBTIS-488: ---------------------------------- Rechecked this - this issue has nothing to do with the IS TP - the issue is that the IS is pulling in the Luna version of Teiid Designer which contains the 1.1.2.Final foundation feature. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/teiiddesigner/9.0.4.Final/features/org.jboss.tools.foundation.security.linux.feature_1.1.2.Final-v20150325-0456-B99.jar > JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-488 > URL: https://issues.jboss.org/browse/JBTIS-488 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > Update site at > http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integration-stack/earlyaccess/ > contains > org.jboss.tools.foundation.security.linux_1.1.2.Final-v20150325-0456-B99 > but JBDS 9 contains org.jboss.tools.foundation.security.linux_1.2.0.Beta2-v20150724-1456-B25. So, if we try to install all features (uncheck 'Group items by category'), we will get an error > Cannot complete the request. See the error log for details. > "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed. > This feature is required by Teiid Designer and it was included in JBTIS-112 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 11:52:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 11:52:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122577#comment-13122577 ] Nick Boldt commented on JBIDE-21012: ------------------------------------ One will discard the other. 20 mins ago, I saw "Latest Build: 1.5.100-SNAPSHOT (Alpha1-v20151026-1942-B311)" in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1.zip-unzip/index.html and https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151026.194304-12-Alpha1.zip contains that same content: "Latest Build: 1.5.100-SNAPSHOT (Alpha1-v20151026-1942-B311)" Then I rebuilt with BUILD_ALIAS=Alpha0 to test this theory: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master/312/parameters/ (Alpha0) http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master/312/console {code} 11:47:35 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151027.154728-13-Alpha0.zip (2944 KB at 2914.6 KB/sec) {code} Now, this URL is 404'd: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1.zip-unzip/ and instead we have these: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha0.zip-unzip/index.html (no longer Alpha1; instead Alpha0) https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT.zip-unzip/index.html (not sure why this has appeared -- wasn't there when I did an Alpha1 build) > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:08:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 12:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers updated JBIDE-16503: ------------------------------ Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) (was: 4.4.x) > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:08:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 12:08:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21028) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: Koen Aers created JBIDE-21028: --------------------------------- Summary: Empty Hibernate Console Configuration dialog Key: JBIDE-21028 URL: https://issues.jboss.org/browse/JBIDE-21028 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate, upstream Affects Versions: 4.2.0.Alpha2 Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 Reporter: Jiri Peterka Assignee: Koen Aers Fix For: 4.4.0.Alpha1 There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:08:01 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 12:08:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21028) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers updated JBIDE-21028: ------------------------------ Fix Version/s: 4.3.1.Beta1 (was: 4.4.0.Alpha1) > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-21028 > URL: https://issues.jboss.org/browse/JBIDE-21028 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.1.Beta1 > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:53:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122630#comment-13122630 ] Nick Boldt commented on JBDS-3547: ---------------------------------- OK, so then my PR should be fine, as it's basically just one simple global substitution: {code}s#http://www.redhat.com/j/elqNow/elqRedir.htm?ref=http#https#g{code} https://github.com/jbosstools/jbosstools-website/pull/524 Please approve and push to prod if you're satisfied w/ the PR and the above explanation, [~akazakov]. > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:54:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3549: ----------------------------- Component/s: docker server > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker, server > Reporter: Max Rydahl Andersen > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:54:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBDS-3549: -------------------------------- Assignee: Rob Stryker > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3552: ----------------------------- Component/s: docker > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBDS-3552: -------------------------------- Assignee: Xavier Coulon > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3549: ----------------------------- Component/s: (was: server) > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:55:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBDS-3549: -------------------------------- Assignee: Xavier Coulon (was: Rob Stryker) > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:55:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:55:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3550: ----------------------------- Component/s: docker > Developer - autodetect the CDK in IDE > ------------------------------------- > > Key: JBDS-3550 > URL: https://issues.jboss.org/browse/JBDS-3550 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > > User Story: > As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use > Acceptance Criteria: > * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect > * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:55:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:55:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBDS-3550: -------------------------------- Assignee: Xavier Coulon > Developer - autodetect the CDK in IDE > ------------------------------------- > > Key: JBDS-3550 > URL: https://issues.jboss.org/browse/JBDS-3550 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > User Story: > As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use > Acceptance Criteria: > * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect > * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:56:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3551: ----------------------------- Component/s: jsp/jsf/xml/html-source-editing > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: jsp/jsf/xml/html-source-editing > Reporter: Max Rydahl Andersen > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 12:56:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 12:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBDS-3551: -------------------------------- Assignee: Alexey Kazakov > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: jsp/jsf/xml/html-source-editing > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 13:39:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Tue, 27 Oct 2015 13:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122647#comment-13122647 ] Len DiMaggio commented on JBDS-3549: ------------------------------------ I think that yo > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 13:41:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Tue, 27 Oct 2015 13:41:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122647#comment-13122647 ] Len DiMaggio edited comment on JBDS-3549 at 10/27/15 1:40 PM: -------------------------------------------------------------- I think that you will also want some (visual) way in the IDE to determine the current status of the CDK. was (Author: ldimaggio): I think that yo > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 13:55:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Tue, 27 Oct 2015 13:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21029) Use newer Easymport (update TP) In-Reply-To: References: Message-ID: Mickael Istria created JBIDE-21029: -------------------------------------- Summary: Use newer Easymport (update TP) Key: JBIDE-21029 URL: https://issues.jboss.org/browse/JBIDE-21029 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: easymport, target-platform Affects Versions: 4.3.1.Beta1 Reporter: Mickael Istria Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final *Reason:* Use new features and fixes (allowing preview of import plan) *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import *Version:* 0.2.0 *License and owner:* EPL, Red Hat Inc. *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ *Include Sources:* Yes *Affected JBoss Tools components:* jbosstools-playground *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 13:57:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Tue, 27 Oct 2015 13:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21029) Use newer Easymport (update TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria reassigned JBIDE-21029: -------------------------------------- Assignee: Mickael Istria > Use newer Easymport (update TP) > ------------------------------- > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 13:57:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Tue, 27 Oct 2015 13:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21029) Use newer Easymport (update TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBIDE-21029: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Use newer Easymport (update TP) > ------------------------------- > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 14:33:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 27 Oct 2015 14:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21025) hibernate querying nor content assist is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21025: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > hibernate querying nor content assist is broken > ----------------------------------------------- > > Key: JBIDE-21025 > URL: https://issues.jboss.org/browse/JBIDE-21025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > using html5-kitchensink I cannot get basic content assist to work. > "from Member m where m.|" gives no content assist at all. > And trying to run the query results in: > {code} > java.lang.NullPointerException > at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1888) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845) > at org.jboss.tools.hibernate.runtime.v_4_3.internal.ConfigurationFacadeImpl.buildTargetSessionFactory(ConfigurationFacadeImpl.java:24) > at org.jboss.tools.hibernate.runtime.common.AbstractConfigurationFacade.buildSessionFactory(AbstractConfigurationFacade.java:169) > at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108) > at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) > 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:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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:483) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 14:56:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 27 Oct 2015 14:56:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21024) webservice tester "forgets" parameterized url In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21024: ----------------------------------- Fix Version/s: 4.3.x 4.4.x > webservice tester "forgets" parameterized url > --------------------------------------------- > > Key: JBIDE-21024 > URL: https://issues.jboss.org/browse/JBIDE-21024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.x, 4.4.x > > > use html5 kitchensink example and one of the urls you can run is "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/{id:[0-9][0-9]*}" > When you run this webservice tester will ask you about id - great. > But when executing the first time it will reset the url to "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/" meaning it is not possible to run again without manually typing it in. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 15:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 27 Oct 2015 15:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3551: --------------------------------- Component/s: docker (was: jsp/jsf/xml/html-source-editing) > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 15:06:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 27 Oct 2015 15:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov reassigned JBDS-3551: ------------------------------------ Assignee: Xavier Coulon (was: Alexey Kazakov) > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 15:17:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 27 Oct 2015 15:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122677#comment-13122677 ] Fred Bricon commented on JBTIS-529: ----------------------------------- OK, so the Fuse wizard is now hidden when EA is disabled (close/reopen central to see it happen). Now looking into problem #2... > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 15:50:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Tue, 27 Oct 2015 15:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122687#comment-13122687 ] Rob Stryker commented on JBIDE-20990: ------------------------------------- Regarding how liveereload does it, I found a bug in upstream that prevents me from using an API i want. There's workarounds though. Just thought i'd link it here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480811 > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 16:05:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 16:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-529: ----------------------------- Fix Version/s: 4.3.0.Alpha2 > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 16:05:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 16:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-529: ----------------------------- Labels: respin-b (was: ) > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 16:27:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Tue, 27 Oct 2015 16:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122696#comment-13122696 ] Nick Boldt commented on JBIDE-21012: ------------------------------------ So... I have no answer here for how to use Nexus for snapshots that don't conflict across the same x.y.z version. And I have no answer for how to publish to the snapshots repo, with automatic unpacking via the unzip plugin, for a deployment which doesn't have -SNAPSHOT in its name. Sure, we could build the update site and call it 4.3.0.Beta5 instead of 4.3.0-SNAPSHOT, but then it gets pushed to the non-public staging Nexus repo for RELEASE (which Jenkins can't directly push to, afaict), not the public snapshots repo. I can currently only think of two possible ways around this: * upversion every time we do a milestone (instead of 4.3.0.Beta1 then 4.3.0.Beta2, we would do 4.3.0 then 4.3.1) * freeze master branch builds until the milestone is built, respun if needed, and released. IMHO neither of these are viable solutions (too much churn, too likely to screw up if a job is accidentally turned back on), so we have no choice but to remove deployment to nexus for JBT component sites. One last option I can see is to figure out a way to convince Jenkins that when it wants to push to /staging/ it REALLY means /snapshots/... perhaps with a Maven config override or settings.xml file? [~mickael_istria] do you know a way to force Maven to push a non-SNAPSHOT versioned artifact to /snapshots/ instead of /staging/ ? > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 16:37:00 2015 From: issues at jboss.org (Koen Aers (JIRA)) Date: Tue, 27 Oct 2015 16:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21028) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Aers resolved JBIDE-21028. ------------------------------- Resolution: Done > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-21028 > URL: https://issues.jboss.org/browse/JBIDE-21028 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.1.Beta1 > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 16:47:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Tue, 27 Oct 2015 16:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21028) Empty Hibernate Console Configuration dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21028: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-21028 > URL: https://issues.jboss.org/browse/JBIDE-21028 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 27 16:54:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Tue, 27 Oct 2015 16:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20521) Show In - Web Browser is enabled and do nothing when there are no routes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122702#comment-13122702 ] Fred Bricon commented on JBIDE-20521: ------------------------------------- [~mlabuda]: do you have an example of route-less project/application/template? [~istewart]: do you mind taking a look please? > Show In - Web Browser is enabled and do nothing when there are no routes > ------------------------------------------------------------------------ > > Key: JBIDE-20521 > URL: https://issues.jboss.org/browse/JBIDE-20521 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Priority: Minor > Fix For: 4.3.1.Beta1 > > > When I am having a project with an application without any route, the Show In - Web Browser context menu of a project is enabled for this project and it does not do anything (after click nothing happens). Context menu should be disable if there are no routes for an application. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 07:59:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 28 Oct 2015 07:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122797#comment-13122797 ] Mickael Istria commented on JBDS-3553: -------------------------------------- I believe this requires to update JBDS target-platform, to add recommenders features to the dependencies of our JBDS feature. > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 08:06:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 28 Oct 2015 08:06:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBDS-3553: --------------------------------- Component/s: target-platform Description: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO {code} was: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 08:29:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 28 Oct 2015 08:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBDS-3553: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/171, https://github.com/jbdevstudio/jbdevstudio-product/pull/346 Suggested PR for TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/171 Suggested PR for product (blocked by TP): https://github.com/jbdevstudio/jbdevstudio-product/pull/346 > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:18:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 28 Oct 2015 09:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122879#comment-13122879 ] Fred Bricon commented on JBDS-3553: ----------------------------------- If you want more than basic java/SWT recommendations, you can install the crowd-based recommendation database (aka Hippie) http://www.codetrails.com/crowd-recommendation-tools/getting-started However, it uses a weird license (mostly because you *can* upload your own API usage stats), that probably requires to be vetted by a lawyer It can be installed from the Eclipse Marketplace or via Preferences > Code Recommenders > Discover new extensions > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:24:01 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 28 Oct 2015 09:24:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122893#comment-13122893 ] Mickael Istria commented on JBDS-3553: -------------------------------------- The crowd-based recommendation isn't the most interesting one IMO, so we could stick with the default configuration but still leverage substring, constructor and chained completions that are IMO already very good. > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: Nick Boldt created JBDS-3554: -------------------------------- Summary: Integrate/Enable CodeRecommenders substring completion in JBDS 10 Key: JBDS-3554 URL: https://issues.jboss.org/browse/JBDS-3554 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: p2-product, target-platform Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 9.0.1.Beta1 Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- Summary: Integrate/Enable CodeRecommenders substring completion in JBDS 9 (was: Integrate/Enable CodeRecommenders substring completion in JBDS) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:30:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:30:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:30:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:30:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:30:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:30:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3553: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:30:03 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:30:03 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- Status: New (was: New) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:31:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:31:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3554: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:31:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:31:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122904#comment-13122904 ] Nick Boldt commented on JBDS-3553: ---------------------------------- I have set CDW acks for PM, QE, and Dev, since those parties have all +1'd above. Are we not using CDW anymore? Also duplicated this issue to JBDS-3554 to track in JBDS 10. > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122905#comment-13122905 ] Nick Boldt commented on JBDS-3554: ---------------------------------- I have set CDW acks for PM, QE, and Dev, since those parties have all +1'd in JBDS-3553. > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3553: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- Target Release: 10.0.0.GA (was: 9.0.1.GA) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.0.1.Beta1) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:32:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:32:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:32:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3553: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:32:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:32:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:33:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:33:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3553: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- Target Release: 9.0.1.GA (was: 10.0.0.GA) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- Fix Version/s: 9.0.1.Beta1 (was: 10.0.0.Alpha1) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3554: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- Target Release: 10.0.0.GA (was: 9.0.1.GA) > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- Fix Version/s: 10.0.0.Alpha1 > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- Fix Version/s: (was: 9.0.1.Beta1) > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3554: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:33:02 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:33:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:35:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:35:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- Status: New (was: New) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:35:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:35:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:35:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:35:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:35:01 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 09:35:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3553: -------------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:35:01 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:35:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3553: ----------------------------- > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122904#comment-13122904 ] Nick Boldt edited comment on JBDS-3553 at 10/28/15 9:35 AM: ------------------------------------------------------------ I have set CDW acks for PM, QE, and Dev, since those parties have all +1'd above. Are we not using CDW anymore? Also duplicated this issue to JBDS-3554 to track in JBDS 10. (Apologies for the JIRA spam - accidentally moved this issue to JBDS 10, not JBDS-3554, so had to set CDW flags again after moving it back. What a pain.) was (Author: nickboldt): I have set CDW acks for PM, QE, and Dev, since those parties have all +1'd above. Are we not using CDW anymore? Also duplicated this issue to JBDS-3554 to track in JBDS 10. > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:37:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21030) Use newer Easymport (update TP) In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-21030: ---------------------------------- Summary: Use newer Easymport (update TP) Key: JBIDE-21030 URL: https://issues.jboss.org/browse/JBIDE-21030 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: easymport, target-platform Affects Versions: 4.3.1.Beta1 Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final *Reason:* Use new features and fixes (allowing preview of import plan) *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import *Version:* 0.2.0 *License and owner:* EPL, Red Hat Inc. *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ *Include Sources:* Yes *Affected JBoss Tools components:* jbosstools-playground *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:37:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21030) Use newer Easymport (update JBDS 10 TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21030: ------------------------------- Summary: Use newer Easymport (update JBDS 10 TP) (was: Use newer Easymport (update TP)) > Use newer Easymport (update JBDS 10 TP) > --------------------------------------- > > Key: JBIDE-21030 > URL: https://issues.jboss.org/browse/JBIDE-21030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:38:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21030) Use newer Easymport (update Neon TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21030: ------------------------------- Summary: Use newer Easymport (update Neon TP) (was: Use newer Easymport (update JBDS 10 TP)) > Use newer Easymport (update Neon TP) > ------------------------------------ > > Key: JBIDE-21030 > URL: https://issues.jboss.org/browse/JBIDE-21030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:38:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21030) Use newer Easymport (update Neon TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21030: ------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > Use newer Easymport (update Neon TP) > ------------------------------------ > > Key: JBIDE-21030 > URL: https://issues.jboss.org/browse/JBIDE-21030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:38:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21030) Use newer Easymport (update Neon TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21030: ------------------------------- Affects Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Use newer Easymport (update Neon TP) > ------------------------------------ > > Key: JBIDE-21030 > URL: https://issues.jboss.org/browse/JBIDE-21030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:38:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21029) Use newer Easymport (update Mars TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21029: ------------------------------- Summary: Use newer Easymport (update Mars TP) (was: Use newer Easymport (update TP)) > Use newer Easymport (update Mars TP) > ------------------------------------ > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:38:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:38:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21029) Use newer Easymport (update Mars TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21029: ------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Use newer Easymport (update Mars TP) > ------------------------------------ > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 09:39:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 09:39:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21029) Use newer Easymport (update Mars TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122908#comment-13122908 ] Nick Boldt commented on JBIDE-21029: ------------------------------------ Cloned to JBIDE-21030 to be fixed in 4.4.0.Alpha1 / 4.60.x TPs. > Use newer Easymport (update Mars TP) > ------------------------------------ > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 10:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/172, https://github.com/jbdevstudio/jbdevstudio-product/pull/348 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/171, https://github.com/jbdevstudio/jbdevstudio-product/pull/346) > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 10:29:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 10:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20936) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20936: ------------------------------- Summary: Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) (was: Unable to import Fuse Integration Project from Central when Fuse toolink isn't installed.) > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20936 > URL: https://issues.jboss.org/browse/JBIDE-20936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 10:30:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 10:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-529: ----------------------------- Description: not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. But even with or without earlyaccess installing via the wizard result in: Problems occurred while performing installation: There are no connectors to install There are no connectors to install /cc [~fbricon] any idea ? was: not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. But even with or without earlyaccess installing via the wizard result in: Problems occurred while performing installation: There are no connectors to install There are no connectors to install /cc [~fbricon] any idea ? > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 10:40:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 28 Oct 2015 10:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122933#comment-13122933 ] Paul Leacu commented on JBTIS-529: ---------------------------------- Problem #2 was actually am error in the requiredComponentIds for the Fuse Integration proxy wizard - - requiredComponentIds="jboss.integration-stack.ea.bundle.fuse"> + requiredComponentIds="jboss.integration-stack.bundle.fuse"> The jar is patched and it is working okay now. [~fbricon] - please double check. I'll ask [~apodhrad] to add JBoss Central proxy wizard verification to the QE testing. A PR will be coming shortly. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 10:44:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 10:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122938#comment-13122938 ] Nick Boldt commented on JBTIS-529: ---------------------------------- First, here's what was done on Friday to patch the IS "Alpha2 renamed from Final/GA" jars, and to move stuff out of "supported and back to "earlyaccess": https://github.com/jbosstools/jbosstools-integration-stack/pull/455 Next, I'll look at verifying we have no conflicting IDs. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 10:54:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 28 Oct 2015 10:54:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122933#comment-13122933 ] Paul Leacu edited comment on JBTIS-529 at 10/28/15 10:53 AM: ------------------------------------------------------------- Problem #2 was actually an error in the requiredComponentIds for the Fuse Integration proxy wizard - - requiredComponentIds="jboss.integration-stack.ea.bundle.fuse"> + requiredComponentIds="jboss.integration-stack.bundle.fuse"> The jar is patched and it is working okay now. [~fbricon] - please double check. I'll ask [~apodhrad] to add JBoss Central proxy wizard verification to the QE testing. A PR will be coming shortly. was (Author: pleacu): Problem #2 was actually am error in the requiredComponentIds for the Fuse Integration proxy wizard - - requiredComponentIds="jboss.integration-stack.ea.bundle.fuse"> + requiredComponentIds="jboss.integration-stack.bundle.fuse"> The jar is patched and it is working okay now. [~fbricon] - please double check. I'll ask [~apodhrad] to add JBoss Central proxy wizard verification to the QE testing. A PR will be coming shortly. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 10:59:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 10:59:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122938#comment-13122938 ] Nick Boldt edited comment on JBTIS-529 at 10/28/15 10:58 AM: ------------------------------------------------------------- First, here's what was done on Friday to patch the IS "Alpha2 renamed from Final/GA" jars, and to move stuff out of "supported and back to "earlyaccess": https://github.com/jbosstools/jbosstools-integration-stack/pull/455 I've also fixed the conflicting IDs and added a missing proxy wizard to JBT IS EA plugin.xml. Please review, [~pleacu] [~fbricon]. Paul: what jar(s) did you patch? Did you rename them to Alpha2b? was (Author: nickboldt): First, here's what was done on Friday to patch the IS "Alpha2 renamed from Final/GA" jars, and to move stuff out of "supported and back to "earlyaccess": https://github.com/jbosstools/jbosstools-integration-stack/pull/455 Next, I'll look at verifying we have no conflicting IDs. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 11:07:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 11:07:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBTIS-529: ----------------------------- Attachment: JBDSIS_EA_Alpha2b_vs_Alpha2a.png JBDSIS_Alpha2b_vs_Alpha2a.png JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png Here's what Paul changed in JBTIS discovery plugins: [^JBDSIS_EA_Alpha2b_vs_Alpha2a.png] [^JBDSIS_Alpha2b_vs_Alpha2a.png] And in both, I see a worrying change in the plugins' MANIFEST.MF files: [^JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png] > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 11:10:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 11:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122954#comment-13122954 ] Nick Boldt edited comment on JBTIS-529 at 10/28/15 11:09 AM: ------------------------------------------------------------- Here's what Paul changed in JBDS IS discovery plugins: [^JBDSIS_EA_Alpha2b_vs_Alpha2a.png] [^JBDSIS_Alpha2b_vs_Alpha2a.png] And in both, I see a worrying change in the plugins' MANIFEST.MF files: [^JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png] For JBTIS, I only see one change: {code} + id="jboss.integration-stack.ea.bundle.generic"> - id="jboss.integration-stack.ea.bundle.fuse"> {code} This is OK, but it's only a partial solution. See my PR for a more complete one. was (Author: nickboldt): Here's what Paul changed in JBTIS discovery plugins: [^JBDSIS_EA_Alpha2b_vs_Alpha2a.png] [^JBDSIS_Alpha2b_vs_Alpha2a.png] And in both, I see a worrying change in the plugins' MANIFEST.MF files: [^JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png] > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 11:10:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 28 Oct 2015 11:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122956#comment-13122956 ] Paul Leacu commented on JBTIS-529: ---------------------------------- Yes - Alpha2b - added plugins and updated directory XMLs: https://devstudio.redhat.com/9.0/stable/updates/discovery.central/9.0.0.GA/plugins/ https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0.0.GA/plugins/ http://download.jboss.org/jbosstools/mars/stable/updates/discovery.central/4.3.0.Final/plugins/ http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/plugins/ I didn't create a org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.3.0.Alpha2b-v20151006-1928-B438.jar because it didn't have a Fuse proxy wizard so it didn't need to be updated. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 11:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 11:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122954#comment-13122954 ] Nick Boldt edited comment on JBTIS-529 at 10/28/15 11:10 AM: ------------------------------------------------------------- Here's what Paul changed in JBDS IS discovery plugins: [^JBDSIS_EA_Alpha2b_vs_Alpha2a.png] [^JBDSIS_Alpha2b_vs_Alpha2a.png] And in both, I see a worrying change in the plugins' MANIFEST.MF files: [^JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png] For JBTIS, I only see one change: {code} + id="jboss.integration-stack.ea.bundle.generic"> - id="jboss.integration-stack.ea.bundle.fuse"> {code} This is OK, but it's only a partial solution. See my PR for a more complete one. Note that this change ALSO caused the same loss of data in the MANIFEST.MF file. So, I think we need a set of Alpha2c plugins which I can create if people approve my PR. was (Author: nickboldt): Here's what Paul changed in JBDS IS discovery plugins: [^JBDSIS_EA_Alpha2b_vs_Alpha2a.png] [^JBDSIS_Alpha2b_vs_Alpha2a.png] And in both, I see a worrying change in the plugins' MANIFEST.MF files: [^JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png] For JBTIS, I only see one change: {code} + id="jboss.integration-stack.ea.bundle.generic"> - id="jboss.integration-stack.ea.bundle.fuse"> {code} This is OK, but it's only a partial solution. See my PR for a more complete one. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 11:14:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 11:14:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122959#comment-13122959 ] Nick Boldt commented on JBTIS-529: ---------------------------------- [~pleacu] http://download.jboss.org/jbosstools/mars/stable/updates/discovery.earlyaccess/4.3.0.Final/jbosstools-directory.xml shows pointers to Alpha2a not Alpha2b. Did you actually update the file? Did you commit your changes to github? I don't see either. :( Re: "didn't create org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.3.0.Alpha2b-v20151006-1928-B438.jar because it didn't have a Fuse proxy wizard so it didn't need to be updated." ... that should have tipped you off to the fact that there was a missing proxy wizard, which SHOULD have been there. See my PR for more. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 11:34:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 28 Oct 2015 11:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122971#comment-13122971 ] Paul Leacu commented on JBTIS-529: ---------------------------------- Okay - I corrected devstudio and tested it first - you caught me before I had a chance to update the jbt directory xmls. I have a PR but it takes some time to build for both jbt and devstudio. As for the fuse proxy wizard - since that was added by the Fuse team I thought they may have a reason for not including it in the community side and thought I should correct the issue at hand with devstudio and see what Lars thinks about adding it. The jars missing data is of interest. What do you use to create the jars - anything specific or just 'jar cvf ...' ?? > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 11:37:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 28 Oct 2015 11:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Istria updated JBDS-3553: --------------------------------- Description: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* {code} mistria at mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ > org.eclipse.recommenders.jdt [2.2.4.v20150914-0857] > org.eclipse.recommenders.overrides [2.2.4.v20150914-0857] > org.eclipse.recommenders.injection [2.2.4.v20150914-0857] > org.eclipse.aether.maven.feature.feature.group [3.1.0.20140706-2237] > org.eclipse.aether.transport.http [1.0.1.v20141111] > org.eclipse.aether.api [1.0.1.v20141111] > org.eclipse.aether.transport.http.feature.feature.jar [1.0.1.v20141111] > org.eclipse.aether.transport.file.feature.feature.jar [1.0.1.v20141111] > org.eclipse.recommenders.overrides.rcp [2.2.4.v20150914-0857] > org.eclipse.recommenders.utils [2.2.4.v20150914-0857] > org.eclipse.aether.connector.basic.feature.feature.jar [1.0.1.v20141111] > org.eclipse.aether.spi [1.0.1.v20141111] > com.google.inject.multibindings [3.0.0.v201402270930] > org.eclipse.recommenders.completion.rcp [2.2.4.v20150914-0857] > org.eclipse.aether.maven.feature.feature.jar [3.1.0.20140706-2237] > org.apache.commons.lang3 [3.1.0.v201403281430] > org.eclipse.aether.feature.feature.group [1.0.1.v20141111] > org.eclipse.recommenders.types.rcp [2.2.4.v20150914-0857] > org.eclipse.recommenders.calls.rcp [2.2.4.v20150914-0857] > org.eclipse.aether.connector.basic.feature.feature.group [1.0.1.v20141111] > org.apache.commons.pool [1.6.0.v201204271246] > org.eclipse.aether.maven [3.1.0.v20140706-2237] > org.eclipse.recommenders.models [2.2.4.v20150914-0857] > org.eclipse.recommenders.jayes [2.2.4.v20150914-0857] > org.eclipse.aether.transport.file [1.0.1.v20141111] > org.apache.commons.math [2.1.0.v201105210652] > org.eclipse.recommenders.coordinates [2.2.4.v20150914-0857] > org.eclipse.recommenders.subwords.rcp [2.2.4.v20150914-0857] > org.eclipse.recommenders.models.rcp [2.2.4.v20150914-0857] > org.eclipse.aether.transport.http.feature.feature.group [1.0.1.v20141111] > org.eclipse.recommenders.chain.rcp [2.2.4.v20150914-0857] > org.eclipse.recommenders.apidocs [2.2.4.v20150914-0857] > org.eclipse.recommenders.rcp.feature.feature.jar [2.2.4.v20150914-0857] > org.eclipse.recommenders.constructors [2.2.4.v20150914-0857] > org.eclipse.recommenders.calls [2.2.4.v20150914-0857] > org.apache.solr.client.solrj [3.5.0.v20150506-0844] > org.eclipse.aether.impl [1.0.1.v20141111] > org.eclipse.recommenders.jayes.io [2.2.4.v20150914-0857] > com.google.inject [3.0.0.v201312141243] > org.eclipse.aether.connector.basic [1.0.1.v20141111] > ch.qos.logback.slf4j [1.0.7.v201505121915] > org.eclipse.aether.util [1.0.1.v20141111] > org.eclipse.recommenders.utils.rcp [2.2.4.v20150914-0857] > org.eclipse.recommenders.net [2.2.4.v20150914-0857] > org.eclipse.recommenders.constructors.rcp [2.2.4.v20150914-0857] > org.eclipse.aether.feature.feature.jar [1.0.1.v20141111] > org.eclipse.recommenders.rcp [2.2.4.v20150914-0857] > org.eclipse.recommenders.apidocs.rcp [2.2.4.v20150914-0857] > org.eclipse.aether.transport.file.feature.feature.group [1.0.1.v20141111] > org.eclipse.recommenders.rcp.feature.feature.group [2.2.4.v20150914-0857] > org.eclipse.recommenders.coordinates.rcp [2.2.4.v20150914-0857] === Summary === file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ contains 51 unique IUs {code} was: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO {code} > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > mistria at mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ > > org.eclipse.recommenders.jdt [2.2.4.v20150914-0857] > > org.eclipse.recommenders.overrides [2.2.4.v20150914-0857] > > org.eclipse.recommenders.injection [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.group [3.1.0.20140706-2237] > > org.eclipse.aether.transport.http [1.0.1.v20141111] > > org.eclipse.aether.api [1.0.1.v20141111] > > org.eclipse.aether.transport.http.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.transport.file.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.overrides.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.utils [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.spi [1.0.1.v20141111] > > com.google.inject.multibindings [3.0.0.v201402270930] > > org.eclipse.recommenders.completion.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.jar [3.1.0.20140706-2237] > > org.apache.commons.lang3 [3.1.0.v201403281430] > > org.eclipse.aether.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.types.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.group [1.0.1.v20141111] > > org.apache.commons.pool [1.6.0.v201204271246] > > org.eclipse.aether.maven [3.1.0.v20140706-2237] > > org.eclipse.recommenders.models [2.2.4.v20150914-0857] > > org.eclipse.recommenders.jayes [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file [1.0.1.v20141111] > > org.apache.commons.math [2.1.0.v201105210652] > > org.eclipse.recommenders.coordinates [2.2.4.v20150914-0857] > > org.eclipse.recommenders.subwords.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.models.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.http.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.chain.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs [2.2.4.v20150914-0857] > > org.eclipse.recommenders.rcp.feature.feature.jar [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls [2.2.4.v20150914-0857] > > org.apache.solr.client.solrj [3.5.0.v20150506-0844] > > org.eclipse.aether.impl [1.0.1.v20141111] > > org.eclipse.recommenders.jayes.io [2.2.4.v20150914-0857] > > com.google.inject [3.0.0.v201312141243] > > org.eclipse.aether.connector.basic [1.0.1.v20141111] > > ch.qos.logback.slf4j [1.0.7.v201505121915] > > org.eclipse.aether.util [1.0.1.v20141111] > > org.eclipse.recommenders.utils.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.net [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.rcp.feature.feature.group [2.2.4.v20150914-0857] > > org.eclipse.recommenders.coordinates.rcp [2.2.4.v20150914-0857] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ contains 51 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 12:58:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 12:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123006#comment-13123006 ] Nick Boldt commented on JBTIS-529: ---------------------------------- I use Beyond Compare, which simply treats the jars like zips (which are just treated as archived folders) and can save changes w/o mauling the manifests. Highly recommended piece of software - worth paying for it too. BTW, I notice that the newer connectors in master branch include KIE features... should that also be pushed into Alpha2x ? > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 13:09:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Wed, 28 Oct 2015 13:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123009#comment-13123009 ] Paul Leacu commented on JBTIS-529: ---------------------------------- I'll have to look into BC. Yes - KIE is added to master. I'm waiting to see what [~lhein] thinks about adding the fuse proxy wizard to JBTIS but even if he does I think this can wait for JBTIS 4.3.0.Beta1. > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 13:31:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 28 Oct 2015 13:31:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123014#comment-13123014 ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- current status video: https://www.dropbox.com/s/hk7ymzf55ttwdmd/cdk_server_adapter.ogv?dl=0 > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 13:37:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Wed, 28 Oct 2015 13:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123019#comment-13123019 ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- A few comments: the created server adapter says "CDK Server Adapter", I think it should just say "Red Hat CDK". There is a vagrant icon - I would leave that out of this server adapter for now. Its not generic vagrant. Similar some of the pages in the wizard says Vagrant server adapter - it should say CDK in this case. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 14:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- Attachment: p2diff.log.txt > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 14:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 14:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBDS-3554: ----------------------------- Description: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* [^p2diff.log.txt] was: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO {code} > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > [^p2diff.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 14:40:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 28 Oct 2015 14:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-21022: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > open of .md files in project examples don't use markdown editor > --------------------------------------------------------------- > > Key: JBIDE-21022 > URL: https://issues.jboss.org/browse/JBIDE-21022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 14:40:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 28 Oct 2015 14:40:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-21022: ----------------------------------- Assignee: Snjezana Peco (was: Fred Bricon) > open of .md files in project examples don't use markdown editor > --------------------------------------------------------------- > > Key: JBIDE-21022 > URL: https://issues.jboss.org/browse/JBIDE-21022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 15:25:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 15:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123050#comment-13123050 ] Nick Boldt commented on JBIDE-20976: ------------------------------------ These problems will have to remain until Neon.0.M3, available on November 13, 2015 [1]. I've reported them upstream here: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=480913 (Web Tools) * https://bugs.eclipse.org/bugs/show_bug.cgi?id=476918 (Platform) [1] https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Schedule > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 15:44:00 2015 From: issues at jboss.org (Mickael Istria (JIRA)) Date: Wed, 28 Oct 2015 15:44:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123058#comment-13123058 ] Mickael Istria commented on JBIDE-21027: ---------------------------------------- The issue comes from the fact that the installation procedure isn't factorized between Central page and Example wizards. Example wizards use a procedure that is not aware of Early Access at all, leading to the issue reported here. The places in example that require a change are: * https://github.com/jbosstools/jbosstools-central/blob/master/central/plugins/org.jboss.tools.central/src/org/jboss/tools/central/editors/GettingStartedHtmlPage.java#L461 * https://github.com/jbosstools/jbosstools-central/blob/master/examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/internal/fixes/PluginFixUIHandler.java#L51 However, there is currently no easy substitution to that call. The InstallAction, in the SoftwarePage would be a good candidate but requires some changes to be consumed by the wizards. Or maybe most of this action should be moved to JBossDiscoveryUi (which is currently not aware of early access neither...) > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 15:47:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 15:47:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20976) Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-20976: ------------------------------- Summary: Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) (was: Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)) > Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_summary_all.html > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 16:05:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Wed, 28 Oct 2015 16:05:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123066#comment-13123066 ] Fred Bricon commented on JBIDE-21027: ------------------------------------- I think it makes sense to move the early access prefs to the discovery plugin > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 16:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 16:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x) In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-21031: ---------------------------------- Summary: Version of AS features in 4.3.x branch is greater than in master (4.4.x) Key: JBIDE-21031 URL: https://issues.jboss.org/browse/JBIDE-21031 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 Reporter: Nick Boldt Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml But in 9.0.0 we had 3.1.0: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml So, in master, we have 3.2.0, which is seen by VW as being a lower version. Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 16:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 16:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21031: ------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 16:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 16:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21031: ---------------------------------- Assignee: Rob Stryker > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 16:36:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 16:36:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21031: ------------------------------- Priority: Blocker (was: Major) > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 16:37:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Wed, 28 Oct 2015 16:37:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21031: ------------------------------- Description: Versionwatch reports [1] that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml But in 9.0.0 we had 3.1.0: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml So, in master, we have 3.2.0, which is seen by VW as being a lower version. Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. [1] https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html and https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html was: Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml But in 9.0.0 we had 3.1.0: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml So, in master, we have 3.2.0, which is seen by VW as being a lower version. Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports [1] that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. > [1] https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html and https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 17:10:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 28 Oct 2015 17:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker reassigned JBIDE-20947: ----------------------------------- Resolution: (was: Done) Assignee: Rob Stryker (was: Nick Boldt) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 17:12:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 28 Oct 2015 17:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker resolved JBIDE-20947. --------------------------------- Resolution: Done Made a new commit, old commit had incorrect jira number. * 784c82b - (HEAD, origin/jbosstools-4.3.x, jbosstools-4.3.x) JBIDE-20947 - fixing bad upversion in maintenance, AS project (40 seconds ago, Rob Stryker) * 648b542 - JBIDE-20974 - Upversion maintenance (8 days ago, Rob Stryker) Also astools was incorrectly upversioned 2 weeks ago in maintenance stream, hence the second commit. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 17:12:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 28 Oct 2015 17:12:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker closed JBIDE-20947. ------------------------------- > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: 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} > > org.jboss.tools > parent > 4.3.1.Beta1-SNAPSHOT > > {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+fixVersion+%3D+%229.0.1.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.1.Beta1%22%29%29+AND+labels+%3D+task] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 17:22:00 2015 From: issues at jboss.org (CDW Engine (JIRA)) Date: Wed, 28 Oct 2015 17:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] CDW Engine reassigned JBDS-3547: -------------------------------- > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 17:22:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 28 Oct 2015 17:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3547: --------------------------------- > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 17:23:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 28 Oct 2015 17:23:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov resolved JBDS-3547. ---------------------------------- Resolution: Done Merged. > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 8.1.1.GA, 9.1.0.Beta1, 9.0.0.GA, 8.1.0.GA, 8.0.0.GA, 7.1.1.GA > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 18:15:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Wed, 28 Oct 2015 18:15:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Stryker closed JBIDE-21031. ------------------------------- Resolution: Done * 784c82b - (HEAD, origin/jbosstools-4.3.x, jbosstools-4.3.x) JBIDE-20947 - fixing bad upversion in maintenance, AS project (64 minutes ago, Rob Stryker) * 648b542 - JBIDE-20974 - Upversion maintenance (8 days ago, Rob Stryker) Forgot to reference this jira. > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports [1] that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.feature/pom.xml > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Final/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. > [1] https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html and https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch_master/latest/report_detailed_all.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 18:42:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 28 Oct 2015 18:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3553: --------------------------------- Labels: new_and_noteworthy (was: ) > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: new_and_noteworthy > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > mistria at mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ > > org.eclipse.recommenders.jdt [2.2.4.v20150914-0857] > > org.eclipse.recommenders.overrides [2.2.4.v20150914-0857] > > org.eclipse.recommenders.injection [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.group [3.1.0.20140706-2237] > > org.eclipse.aether.transport.http [1.0.1.v20141111] > > org.eclipse.aether.api [1.0.1.v20141111] > > org.eclipse.aether.transport.http.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.transport.file.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.overrides.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.utils [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.spi [1.0.1.v20141111] > > com.google.inject.multibindings [3.0.0.v201402270930] > > org.eclipse.recommenders.completion.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.jar [3.1.0.20140706-2237] > > org.apache.commons.lang3 [3.1.0.v201403281430] > > org.eclipse.aether.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.types.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.group [1.0.1.v20141111] > > org.apache.commons.pool [1.6.0.v201204271246] > > org.eclipse.aether.maven [3.1.0.v20140706-2237] > > org.eclipse.recommenders.models [2.2.4.v20150914-0857] > > org.eclipse.recommenders.jayes [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file [1.0.1.v20141111] > > org.apache.commons.math [2.1.0.v201105210652] > > org.eclipse.recommenders.coordinates [2.2.4.v20150914-0857] > > org.eclipse.recommenders.subwords.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.models.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.http.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.chain.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs [2.2.4.v20150914-0857] > > org.eclipse.recommenders.rcp.feature.feature.jar [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls [2.2.4.v20150914-0857] > > org.apache.solr.client.solrj [3.5.0.v20150506-0844] > > org.eclipse.aether.impl [1.0.1.v20141111] > > org.eclipse.recommenders.jayes.io [2.2.4.v20150914-0857] > > com.google.inject [3.0.0.v201312141243] > > org.eclipse.aether.connector.basic [1.0.1.v20141111] > > ch.qos.logback.slf4j [1.0.7.v201505121915] > > org.eclipse.aether.util [1.0.1.v20141111] > > org.eclipse.recommenders.utils.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.net [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.rcp.feature.feature.group [2.2.4.v20150914-0857] > > org.eclipse.recommenders.coordinates.rcp [2.2.4.v20150914-0857] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ contains 51 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 28 18:51:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Wed, 28 Oct 2015 18:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21029) Use newer Easymport (update Mars TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123084#comment-13123084 ] Alexey Kazakov commented on JBIDE-21029: ---------------------------------------- +1 > Use newer Easymport (update Mars TP) > ------------------------------------ > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 03:20:00 2015 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Labuda_=28JIRA=29?=) Date: Thu, 29 Oct 2015 03:20:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20521) Show In - Web Browser is enabled and do nothing when there are no routes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123115#comment-13123115 ] Mari?n Labuda commented on JBIDE-20521: --------------------------------------- [~fbricon] I don't have an example or anything particular in my mind, but let's just imagine there would be an OpenShift application without WEB UI which would provide capabilities of a server and just clients would be accessing it to process their requests. Or any other application. Well, honestly, I am not sure if this is real use case or could be. > Show In - Web Browser is enabled and do nothing when there are no routes > ------------------------------------------------------------------------ > > Key: JBIDE-20521 > URL: https://issues.jboss.org/browse/JBIDE-20521 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Mari?n Labuda > Priority: Minor > Fix For: 4.3.1.Beta1 > > > When I am having a project with an application without any route, the Show In - Web Browser context menu of a project is enabled for this project and it does not do anything (after click nothing happens). Context menu should be disable if there are no routes for an application. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 04:33:00 2015 From: issues at jboss.org (Yue Wang (JIRA)) Date: Thu, 29 Oct 2015 04:33:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21032) Parameter table is empty when new app with local templates In-Reply-To: References: Message-ID: Yue Wang created JBIDE-21032: -------------------------------- Summary: Parameter table is empty when new app with local templates Key: JBIDE-21032 URL: https://issues.jboss.org/browse/JBIDE-21032 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Environment: 3.1.0.Beta1-v20151023-2117-B60 Reporter: Yue Wang When new app from local templates with application wizard, no parameters is displayed in Templates Parameters table. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 04:35:00 2015 From: issues at jboss.org (Yue Wang (JIRA)) Date: Thu, 29 Oct 2015 04:35:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21032) Application wizard: Parameter table is empty when new app with local templates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yue Wang updated JBIDE-21032: ----------------------------- Summary: Application wizard: Parameter table is empty when new app with local templates (was: Parameter table is empty when new app with local templates) > Application wizard: Parameter table is empty when new app with local templates > ------------------------------------------------------------------------------ > > Key: JBIDE-21032 > URL: https://issues.jboss.org/browse/JBIDE-21032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: 3.1.0.Beta1-v20151023-2117-B60 > Reporter: Yue Wang > Labels: application_wizard, openshift_v3 > > When new app from local templates with application wizard, no parameters is displayed in Templates Parameters table. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 08:55:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Thu, 29 Oct 2015 08:55:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123292#comment-13123292 ] Paul Leacu commented on JBTIS-529: ---------------------------------- Hey [~fbricon] - this appears to be resolved to me: https://github.com/jbosstools/jbosstools-integration-stack/commit/6904f231cb9e5300cf5076150cdfdc92ecdb0b52 https://github.com/jbosstools/jbosstools-integration-stack/commit/deed7bbf1f273eb8cc98e921f5c07ceb8a088dd4 > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 10:32:01 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 29 Oct 2015 10:32:01 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky updated JBTIS-517: ------------------------------------ Attachment: jbdsis9_webpage_2015_10_29.png jbdsis9_ea_webpage_2015_10_29.png > Update web pages for JBDS-IS 9.x > -------------------------------- > > Key: JBTIS-517 > URL: https://issues.jboss.org/browse/JBTIS-517 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.Alpha2 > > Attachments: jbdsis-900alpha2-webpage.png, jbdsis-900alpha2ea-webpage.png, jbdsis9_ea_webpage_2015_10_29.png, jbdsis9_webpage_2015_10_29.png > > > Update web pages for JBDS-IS 9.x at > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ > See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 10:43:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 29 Oct 2015 10:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-480) JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final - update jbosstools/devstudio infrastructure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrej Podhradsky closed JBTIS-480. ----------------------------------- > JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final - update jbosstools/devstudio infrastructure > ------------------------------------------------------------------------------- > > Key: JBTIS-480 > URL: https://issues.jboss.org/browse/JBTIS-480 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.3.GA, 4.2.3.Final > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.3.GA, 4.2.3.Final > > > Update jbosstools-download.jboss.org and jbdevstudio-website with 4.2.3.Final/ 8.0.3.GA distribution infrastructure. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 10:43:00 2015 From: issues at jboss.org (Andrej Podhradsky (JIRA)) Date: Thu, 29 Oct 2015 10:43:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-466) JBTIS 4.2.3.Final component updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123423#comment-13123423 ] Andrej Podhradsky commented on JBTIS-466: ----------------------------------------- Verified with JBDS 8.1.0.GA + JBDS-IS 8.0.3.GA > JBTIS 4.2.3.Final component updates > ----------------------------------- > > Key: JBTIS-466 > URL: https://issues.jboss.org/browse/JBTIS-466 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 4.2.3.Final > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.3.Final > > > Component updated to JBTIS composites and discovery metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 11:46:00 2015 From: issues at jboss.org (Denis Golovin (JIRA)) Date: Thu, 29 Oct 2015 11:46:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123479#comment-13123479 ] Denis Golovin commented on JBIDE-20442: --------------------------------------- [~vpakan], do you have something to look at or run? > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-tern-mirror/) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 12:58:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Thu, 29 Oct 2015 12:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20982) JBDS consumes 40-50% CPU without any noticeable job in progress In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123522#comment-13123522 ] Snjezana Peco commented on JBIDE-20982: --------------------------------------- I can't reproduce the issue on Linux and Windows. Importing 200+ javaee7-samples projects takes a long time. Once they are imported, Eclipse/Java consumes 2+ GB RAM, but a minimal percent (<1%) of CPU. I can't test on Mac. Try to test Eclipse Mars and some newer JDK. > JBDS consumes 40-50% CPU without any noticeable job in progress > --------------------------------------------------------------- > > Key: JBIDE-20982 > URL: https://issues.jboss.org/browse/JBIDE-20982 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: jstack-JBDS-3147-1.txt, jstack-JBDS-3147-2.txt, jstack-JBDS-3147-3.txt, jstack-JBDS-3147-4.txt, Screen Shot 2014-09-11 at 16.06.20.png, Screen Shot 2014-09-12 at 09.22.31.png, Screen Shot 2014-09-12 at 12.33.40.png, Screen Shot 2014-09-12 at 17.49.48.png > > > Steps to reproduce (on MacOSX): > - import all WildFly Quickstarts (https://github.com/wildfly/quickstart) > - restart the workbench > - once all projects have been built and no job appears in the progress view, JBDS still consumes ~40% a CPU -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 13:34:00 2015 From: issues at jboss.org (Burr Sutter (JIRA)) Date: Thu, 29 Oct 2015 13:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123529#comment-13123529 ] Burr Sutter commented on JBIDE-20990: ------------------------------------- Concerning "Red Hat CDK" - at what point does this string become permanent? It is possible we will have another name in the future. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 14:53:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 29 Oct 2015 14:53:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18327) Add a "Open Log" button in the Forge Console In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi closed JBIDE-18327. ----------------------------------- Fix Version/s: (was: 4.2.x) Resolution: Won't Fix Eclipse Error Log already logs the errors occurred in Forge > Add a "Open Log" button in the Forge Console > -------------------------------------------- > > Key: JBIDE-18327 > URL: https://issues.jboss.org/browse/JBIDE-18327 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: George Gastaldi > Priority: Trivial > > This would open the {{~/.forge/log/forge.log}} file when clicked -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 14:58:00 2015 From: issues at jboss.org (George Gastaldi (JIRA)) Date: Thu, 29 Oct 2015 14:58:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-18178) Forge Console throws exception when UP is kept pressed for some time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-18178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi resolved JBIDE-18178. ------------------------------------- Resolution: Out of Date Cannot reproduce anymore. Looks like it's outdated. > Forge Console throws exception when UP is kept pressed for some time > -------------------------------------------------------------------- > > Key: JBIDE-18178 > URL: https://issues.jboss.org/browse/JBIDE-18178 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Priority: Minor > Fix For: 4.2.x > > > {code} > java.lang.Throwable: Unimplemented command: CURSOR_UP > at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:18) > at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:22) > at org.jboss.tools.aesh.core.internal.io.DocumentInputOutputHandler.handleCommand(DocumentInputOutputHandler.java:42) > at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:50) > at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:27) > at java.io.PrintStream.write(PrintStream.java:480) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104) > at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185) > at java.io.PrintStream.write(PrintStream.java:527) > at java.io.PrintStream.print(PrintStream.java:669) > at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:207) > at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:128) > at org.jboss.aesh.console.AeshInputProcessor.getHistoryElement(AeshInputProcessor.java:420) > at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:164) > at org.jboss.aesh.console.Console.processInternalOperation(Console.java:615) > at org.jboss.aesh.console.Console.execute(Console.java:605) > at org.jboss.aesh.console.Console.access$700(Console.java:58) > at org.jboss.aesh.console.Console$6.run(Console.java:508) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 15:17:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Thu, 29 Oct 2015 15:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123551#comment-13123551 ] Paul Leacu commented on JBTIS-508: ---------------------------------- Release guide updated: https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/IS_release_process.adoc > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 16:03:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Thu, 29 Oct 2015 16:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123561#comment-13123561 ] Paul Leacu commented on JBTIS-517: ---------------------------------- ok - try it again [~apodhrad] - thkx! > Update web pages for JBDS-IS 9.x > -------------------------------- > > Key: JBTIS-517 > URL: https://issues.jboss.org/browse/JBTIS-517 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.Alpha2 > > Attachments: jbdsis-900alpha2-webpage.png, jbdsis-900alpha2ea-webpage.png, jbdsis9_ea_webpage_2015_10_29.png, jbdsis9_webpage_2015_10_29.png > > > Update web pages for JBDS-IS 9.x at > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/ > See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 16:22:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Thu, 29 Oct 2015 16:22:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-526) JBDSIS on marketplace contains category for WTP patches In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Leacu resolved JBTIS-526. ------------------------------ Fix Version/s: 8.0.3.GA Resolution: Done Don't know how that got in there... > JBDSIS on marketplace contains category for WTP patches > ------------------------------------------------------- > > Key: JBTIS-526 > URL: https://issues.jboss.org/browse/JBTIS-526 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.3.GA > Environment: Eclipse Luna JEE SR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 8.0.3.GA > > Attachments: jbdsis803_marketplace_features.png > > > JBDSIS on marketplace contains category for WTP patches. Is this really intended (see the attached screenshot)? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 17:17:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 29 Oct 2015 17:17:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3549: --------------------------------- Fix Version/s: 10.0.0.Alpha1 > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 17:18:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 29 Oct 2015 17:18:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3550: --------------------------------- Fix Version/s: 9.0.1.Beta1 10.0.0.Alpha1 > Developer - autodetect the CDK in IDE > ------------------------------------- > > Key: JBDS-3550 > URL: https://issues.jboss.org/browse/JBDS-3550 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.0.1.Beta1, 10.0.0.Alpha1 > > > User Story: > As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use > Acceptance Criteria: > * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect > * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 17:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 29 Oct 2015 17:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3551: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 17:25:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Thu, 29 Oct 2015 17:25:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBDS-3552: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 22:29:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 29 Oct 2015 22:29:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123598#comment-13123598 ] Rob Stryker commented on JBIDE-20990: ------------------------------------- Everything here is PoC for now. None of these strings are permanent until they're in a GA release... and even then I'd imagine they can be changed with some annoyance to docs team. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 22:42:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Thu, 29 Oct 2015 22:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test In-Reply-To: References: Message-ID: Len DiMaggio created JBIDE-21033: ------------------------------------ Summary: Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test Key: JBIDE-21033 URL: https://issues.jboss.org/browse/JBIDE-21033 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.3.0.Final Reporter: Len DiMaggio -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 22:42:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Thu, 29 Oct 2015 22:42:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio reassigned JBIDE-21033: ------------------------------------ Assignee: Len DiMaggio > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 22:50:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Thu, 29 Oct 2015 22:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123599#comment-13123599 ] Len DiMaggio commented on JBIDE-21033: -------------------------------------- https://github.com/jbosstools/jbosstools-integration-tests/pull/1221 > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 22:51:00 2015 From: issues at jboss.org (Max Rydahl Andersen (JIRA)) Date: Thu, 29 Oct 2015 22:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123600#comment-13123600 ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- [~burrsutter] btw. if we could avoid having different names for this thing in community vs product that would be great - i.e. its ADB in community and CDK in product. Would be good if we could have a common name to refer to it. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 23:32:00 2015 From: issues at jboss.org (Rob Stryker (JIRA)) Date: Thu, 29 Oct 2015 23:32:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21034) new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list In-Reply-To: References: Message-ID: Rob Stryker created JBIDE-21034: ----------------------------------- Summary: new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list Key: JBIDE-21034 URL: https://issues.jboss.org/browse/JBIDE-21034 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.3.0.Final Reporter: Rob Stryker Small coding error causes a new runtime detector to not have its default enablement respected if a user has previously modified the enablement of any detector. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 04:57:00 2015 From: issues at jboss.org (Vlado Pakan (JIRA)) Date: Fri, 30 Oct 2015 04:57:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123637#comment-13123637 ] Vlado Pakan commented on JBIDE-20442: ------------------------------------- Nothing from test scenarios above is implemented. I have test checking code assist for AngularJS attributes 'ng-*' but I don't know if that is coming from Tern > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-tern-mirror/) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 05:16:00 2015 From: issues at jboss.org (Martin Malina (JIRA)) Date: Fri, 30 Oct 2015 05:16:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123650#comment-13123650 ] Martin Malina commented on JBIDE-20845: --------------------------------------- [~snjeza], I tried again now. And you are right, when I uncheck "Warn when unable to install breakpoint...", it will no longer complain and when I click "List Members" in the web app, it will hit the breakpoint. But there are still a few questions: 1. Why does it display the warning in the first place? It seems that the breakpoint works fine, so why is Eclipse complaining (unless you make turn off the warning)? 2. Why do I need to click the "List Members" button in the web app to trigger this when [~vpakan] allegedly didn't have to do that. Now I actually tend to think that Vlado must have had the breakpoint somewhere else, because it seems to make sense to me that the listAllMembers method is only called when you want to list the members. > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 07:24:00 2015 From: issues at jboss.org (Ilya Buziuk (JIRA)) Date: Fri, 30 Oct 2015 07:24:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20842) Need to implement npm support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123721#comment-13123721 ] Ilya Buziuk commented on JBIDE-20842: ------------------------------------- PR was sent - https://github.com/jbosstools/jbosstools-jst/pull/549 - "npm Init" New wizard for package.json creation - "npm Update" & "npm Install" launch shortcuts - Initial SWTBot tests (org.jboss.tools.jst.js.node.test plugin) > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 09:03:02 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 30 Oct 2015 09:03:02 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20923: ----------------------------------- Assignee: Fred Bricon > Wrong archetype is picked for unreleased EAP (7) > ------------------------------------------------ > > Key: JBIDE-20923 > URL: https://issues.jboss.org/browse/JBIDE-20923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Fred Bricon > > When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype). > Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 09:04:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Fri, 30 Oct 2015 09:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon updated JBIDE-20923: -------------------------------- Fix Version/s: 4.3.1.Beta1 > Wrong archetype is picked for unreleased EAP (7) > ------------------------------------------------ > > Key: JBIDE-20923 > URL: https://issues.jboss.org/browse/JBIDE-20923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype). > Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 11:50:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 30 Oct 2015 11:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123902#comment-13123902 ] Snjezana Peco commented on JBIDE-20845: --------------------------------------- {quote} 1. Why does it display the warning in the first place? It seems that the breakpoint works fine, so why is Eclipse complaining (unless you make turn off the warning)? {quote} Eclipse sets that by default. {quote} 2. Why do I need to click the "List Members" button in the web app to trigger this when Vlado Pakan allegedly didn't have to do that. Now I actually tend to think that Vlado must have had the breakpoint somewhere else, because it seems to make sense to me that the listAllMembers method is only called when you want to list the members. {quote} I have set a breakpoint to MemberService.listAllMembers() (line 72). I don't have to click the "List Members" button no matter whether the "Warn when unable to install breakpoint..." checkbox is checked or not. Could you try again in a new workspace? > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 12:10:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 12:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0 In-Reply-To: References: Message-ID: Nick Boldt created JBIDE-21035: ---------------------------------- Summary: Build with Tycho 0.24.0 Key: JBIDE-21035 URL: https://issues.jboss.org/browse/JBIDE-21035 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 Reporter: Nick Boldt {quote} Tycho milestone 0.24.0 has been released and is available from maven central. See the release notes [1] for details of enhancements and bug fixes in this release. Thanks to: Alexander Kurtakov Lars Vogel Mickael Istria Mikolaj Izdebski who contributed patches for this release. And thanks and to everyone who helped us with testing the staged version. Regards, Tycho team [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 12:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 12:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21035: ------------------------------- Issue Type: Task (was: Bug) > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 12:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 12:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt reassigned JBIDE-21035: ---------------------------------- Assignee: Nick Boldt > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 12:11:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 12:11:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt updated JBIDE-21035: ------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 12:49:00 2015 From: issues at jboss.org (Snjezana Peco (JIRA)) Date: Fri, 30 Oct 2015 12:49:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123933#comment-13123933 ] Snjezana Peco commented on JBIDE-20845: --------------------------------------- See http://screencast.com/t/vNYWg1Bps > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 15:09:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 30 Oct 2015 15:09:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20842) Need to implement npm support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-20842: ----------------------------------- Description: Initially npm support should include the following commands: 1) [init|https://docs.npmjs.com/cli/init] - package.json creation 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder See a short demo: https://vimeo.com/143263045 was: Initially npm support should include the following commands: 1) [init|https://docs.npmjs.com/cli/init] - package.json creation 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder > See a short demo: https://vimeo.com/143263045 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 15:34:00 2015 From: issues at jboss.org (Paul Leacu (JIRA)) Date: Fri, 30 Oct 2015 15:34:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124015#comment-13124015 ] Paul Leacu commented on JBTIS-508: ---------------------------------- Luna now updated - I think we're done with this Jira. The working URLs after updating the IS are clean. https://github.com/jbosstools/jbosstools-download.jboss.org/commit/78646f86c1de8811955df83a1fe8ed4987687100 https://github.com/jbdevstudio/jbdevstudio-website/commit/5663364be88cb88b395dc2db6874f8b8846eb5ef > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 16:01:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 16:01:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21030) Use newer Easymport (update Neon TP) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBIDE-21030. -------------------------------- Resolution: Done PR merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >= 465 > Use newer Easymport (update Neon TP) > ------------------------------------ > > Key: JBIDE-21030 > URL: https://issues.jboss.org/browse/JBIDE-21030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20151014-1740-SNAPSHOT/ > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 16:03:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 16:03:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBDS-3554. ------------------------------ Resolution: Done PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_master/build >= 4106 > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > [^p2diff.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 16:04:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 16:04:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Boldt resolved JBDS-3553. ------------------------------ Resolution: Done PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/devstudio.product_9.0.mars/build >= 131 > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: new_and_noteworthy > Fix For: 9.1.0.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > mistria at mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ > > org.eclipse.recommenders.jdt [2.2.4.v20150914-0857] > > org.eclipse.recommenders.overrides [2.2.4.v20150914-0857] > > org.eclipse.recommenders.injection [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.group [3.1.0.20140706-2237] > > org.eclipse.aether.transport.http [1.0.1.v20141111] > > org.eclipse.aether.api [1.0.1.v20141111] > > org.eclipse.aether.transport.http.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.transport.file.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.overrides.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.utils [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.spi [1.0.1.v20141111] > > com.google.inject.multibindings [3.0.0.v201402270930] > > org.eclipse.recommenders.completion.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.jar [3.1.0.20140706-2237] > > org.apache.commons.lang3 [3.1.0.v201403281430] > > org.eclipse.aether.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.types.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.group [1.0.1.v20141111] > > org.apache.commons.pool [1.6.0.v201204271246] > > org.eclipse.aether.maven [3.1.0.v20140706-2237] > > org.eclipse.recommenders.models [2.2.4.v20150914-0857] > > org.eclipse.recommenders.jayes [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file [1.0.1.v20141111] > > org.apache.commons.math [2.1.0.v201105210652] > > org.eclipse.recommenders.coordinates [2.2.4.v20150914-0857] > > org.eclipse.recommenders.subwords.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.models.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.http.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.chain.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs [2.2.4.v20150914-0857] > > org.eclipse.recommenders.rcp.feature.feature.jar [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls [2.2.4.v20150914-0857] > > org.apache.solr.client.solrj [3.5.0.v20150506-0844] > > org.eclipse.aether.impl [1.0.1.v20141111] > > org.eclipse.recommenders.jayes.io [2.2.4.v20150914-0857] > > com.google.inject [3.0.0.v201312141243] > > org.eclipse.aether.connector.basic [1.0.1.v20141111] > > ch.qos.logback.slf4j [1.0.7.v201505121915] > > org.eclipse.aether.util [1.0.1.v20141111] > > org.eclipse.recommenders.utils.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.net [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.rcp.feature.feature.group [2.2.4.v20150914-0857] > > org.eclipse.recommenders.coordinates.rcp [2.2.4.v20150914-0857] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ contains 51 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 16:10:00 2015 From: issues at jboss.org (Nick Boldt (JIRA)) Date: Fri, 30 Oct 2015 16:10:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124022#comment-13124022 ] Nick Boldt edited comment on JBDS-3554 at 10/30/15 4:09 PM: ------------------------------------------------------------ PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_master/build >= 4107 was (Author: nickboldt): PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_master/build >= 4106 > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > [^p2diff.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 16:21:00 2015 From: issues at jboss.org (Len DiMaggio (JIRA)) Date: Fri, 30 Oct 2015 16:21:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Len DiMaggio resolved JBIDE-21033. ---------------------------------- Fix Version/s: 4.3.0.Final Resolution: Done > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 18:30:00 2015 From: issues at jboss.org (Viacheslav Kabanovich (JIRA)) Date: Fri, 30 Oct 2015 18:30:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21036) Infinite cycle in ParametedType.isAssignableTo() In-Reply-To: References: Message-ID: Viacheslav Kabanovich created JBIDE-21036: --------------------------------------------- Summary: Infinite cycle in ParametedType.isAssignableTo() Key: JBIDE-21036 URL: https://issues.jboss.org/browse/JBIDE-21036 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.3.0.Final Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.1.Beta1 java.lang.StackOverflowError is reported in http://stackoverflow.com/questions/33301776/an-internal-error-occurred-during-jboss-tools-project-validator Infinitely cycling calls are org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:398) at org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:402) at org.jboss.tools.common.java.ParametedType.areTypeParametersAssignableTo(ParametedType.java:430) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 20:27:00 2015 From: issues at jboss.org (Alexey Kazakov (JIRA)) Date: Fri, 30 Oct 2015 20:27:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-21036) Infinite cycle in ParametedType.isAssignableTo() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-21036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kazakov updated JBIDE-21036: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Infinite cycle in ParametedType.isAssignableTo() > ------------------------------------------------ > > Key: JBIDE-21036 > URL: https://issues.jboss.org/browse/JBIDE-21036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > java.lang.StackOverflowError is reported in > http://stackoverflow.com/questions/33301776/an-internal-error-occurred-during-jboss-tools-project-validator > Infinitely cycling calls are > org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:398) at org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:402) at org.jboss.tools.common.java.ParametedType.areTypeParametersAssignableTo(ParametedType.java:430) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 31 00:50:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Sat, 31 Oct 2015 00:50:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Bricon reassigned JBIDE-20571: ----------------------------------- Assignee: Jeff Cantrill > OpenShift Explorer: Build/Pod activity should be refreshed automatically > ------------------------------------------------------------------------ > > Key: JBIDE-20571 > URL: https://issues.jboss.org/browse/JBIDE-20571 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes. > We need to be able to let the explorer "watch" some specific project events (via websockets or some other method). > As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Oct 31 00:51:00 2015 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Sat, 31 Oct 2015 00:51:00 -0400 (EDT) Subject: [jbosstools-issues] [JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124050#comment-13124050 ] Fred Bricon commented on JBIDE-20571: ------------------------------------- assigning to [~jcantrill] since he's implementing watch support in the rest client > OpenShift Explorer: Build/Pod activity should be refreshed automatically > ------------------------------------------------------------------------ > > Key: JBIDE-20571 > URL: https://issues.jboss.org/browse/JBIDE-20571 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes. > We need to be able to let the explorer "watch" some specific project events (via websockets or some other method). > As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)