[JBoss JIRA] (JBDS-3555) Integrate/Enable crowdbase completion in JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3555?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3555:
--------------------------------------
[~nickboldt] It's mainly about update the TP and .product to include the necessary feature. Do you want to take care of it?
[~akazakov] [~fbricon] [~maxandersen] Weren't there some legal things to check first, in order to include the necessary database to make this relevant? Also, is the default code DB satisfying for our typical users, ie does it address the usual APIs our users are using?
> Integrate/Enable crowdbase completion in JBDS
> ---------------------------------------------
>
> Key: JBDS-3555
> URL: https://issues.jboss.org/browse/JBDS-3555
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: p2-product, target-platform
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Fix For: 9.x, 10.x
>
>
> [~fbricon] (from the comment in JBDS-3553):
> {quote}
> 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
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20070) Fix minor issues in RedDeer import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20070?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-20070.
------------------------------------
Fix Version/s: 4.3.1.Beta1
4.4.0.Alpha1
(was: 4.3.x)
Resolution: Done
The new workflow for easymport fixes this user-story.
> Fix minor issues in RedDeer import
> ----------------------------------
>
> Key: JBIDE-20070
> URL: https://issues.jboss.org/browse/JBIDE-20070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
> Attachments: dialog.png
>
>
> When I try to import the whole RedDeer project (cloned from https://github.com/jboss-reddeer/reddeer.git) I can see that some folders have listed "Maven, Java" and some only "Maven" even though the directory structure seems the same to me (e.g. directory "plugins" and directory "features" contain only one pom file and set of other folders, but one has "Java" listed and one does not).
> List of minor issues:
> - the root folder (reddeer) has listed Maven, Eclipse project - I think the Eclipse project should not be there
> - features has listed "Maven" but plugins and tests have "Maven, Java"
> - all plugins in tests folder are correctly recognized as OSGI bundles except for the org.jboss.reddeer.workbench.test that has also "Java" nature
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-21105:
------------------------------------------------
{quote}(2015-11-20 10:59:42) nickboldt: do you want me to try to include the 9.3.5 versions of the two plugins that Birt needs, instead of the 9.2.9 versions?
(2015-11-20 11:01:58) akazakov: nickboldt, yes
(2015-11-20 11:02:34) akazakov: nickboldt, I just doubt that 9.2.9 and 9.3.5 can so-exist safely
(2015-11-20 11:03:05) nickboldt: akazakov: well, it's only 2 plugins
(2015-11-20 11:03:44) nickboldt: and we (anything in JBT/JBDS) don't depend on jetty.osgi.boot or jetty.deploy... it's just birt that needs them
(2015-11-20 11:03:51) nickboldt: but I can see if moving to 9.3.5 works{quote}
If you will look into jetty.deploy you will notice that it requires a lot of jetty plugins. So actually it's not only two plugins. It looks like they don't ship any other plugins because they should be shipped by Eclipse. Bad news is that this approach will not work starting from 9.3.4(actually from 9.3.5 since there is only RC1 for 9.3.4). Can we do something for them?
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21044) Error when trying to import Thym or JS project
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21044?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-21044.
------------------------------------
Resolution: Done
> Error when trying to import Thym or JS project
> ----------------------------------------------
>
> Key: JBIDE-21044
> URL: https://issues.jboss.org/browse/JBIDE-21044
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, easymport, target-platform
> Affects Versions: 4.3.1.Beta1
> Environment: Nightly jboss-devstudio-9.0.1.Beta1-v20151101-1911-B132 with Hybrid mobile tools installed
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When I try to import the kitchensink-cordova example for the 2nd time, an error occurs and the following error is logged.
> {code}
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:478)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.updateTreeContent(ImportProposalsWizardPage.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.pageChanged(ImportProposalsWizardPage.java:221)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1234)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> 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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.execute(OpenFolderCommand.java:91)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.lang.AbstractMethodError
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.getImportProposals(EasymportJob.java:548)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$8.run(ImportProposalsWizardPage.java:188)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> ... 72 more
> Root exception:
> java.lang.AbstractMethodError
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.getImportProposals(EasymportJob.java:548)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$8.run(ImportProposalsWizardPage.java:188)
> 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.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.updateTreeContent(ImportProposalsWizardPage.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.pageChanged(ImportProposalsWizardPage.java:221)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1234)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> 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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.execute(OpenFolderCommand.java:91)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20900:
----------------------------------------
How much to we use permissions? I believe that for those scripts, since we invoke them in a bash step, the only necessary permission is read, which is part of unzip's default.
If so, is there actually an issue here? I'm tempted to close this Jira as rejected.
> 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/jb...
> [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
> [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (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)
10 years, 4 months
[JBoss JIRA] (JBIDE-21123) Port forwarding: Free ports for port forwarding are cached even though dialog was canceled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21123?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21123:
-------------------------------------
Fix Version/s: 4.3.1.Beta1
> Port forwarding: Free ports for port forwarding are cached even though dialog was canceled
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21123
> URL: https://issues.jboss.org/browse/JBIDE-21123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.Beta1
>
>
> In Port forwarding dialog there is a checkbox to use free ports for port forwading. Upon checking this checkbox, free port are used in a table showing services. If user check the checkbox, free ports are used but then cancel the dialog either by pressing Esc or close the dialog, the state of checkbox is cached. If then user opens a dialog again checkbox is not checked but dialog is behaving like it is, because there are used free ports for port forwading. It forces user to check checkbox again, it finds another free ports and then uncheck it to get to default state.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21122) Port Forwarding: Start All button should be disabled if port forwarding is already active
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21122?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21122:
-------------------------------------
Labels: openshift_v3 port_forwarding_wizard (was: openshift_v3)
> Port Forwarding: Start All button should be disabled if port forwarding is already active
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-21122
> URL: https://issues.jboss.org/browse/JBIDE-21122
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.Beta1
>
>
> In Port Forwarding wizard is a button "Start All" which starts port forwarding for all services listed in a table. If user triggers the button and port forwarding is already active, Start All is still enabled and user can click on it again and again but nothing happens. Accessibility of this button should be similar as Stop All, which works as expected - if port forwarding is not active, it is disabled, otherwise it is enabled.
> There is also a checkbox to find free ports for port forwarding. Once port forwarding is active, checking and unchecking this checkbox do nothing. It should have same accessibility as Start All button - if there is active port forwarding, the checkbox should be disabled, otherwise it should be enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21123) Port forwarding: Free ports for port forwarding are cached even though dialog was canceled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21123?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21123:
-------------------------------------
Labels: port_forwarding_wizard (was: )
> Port forwarding: Free ports for port forwarding are cached even though dialog was canceled
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21123
> URL: https://issues.jboss.org/browse/JBIDE-21123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: openshift_v3, port_forwarding_wizard
>
> In Port forwarding dialog there is a checkbox to use free ports for port forwading. Upon checking this checkbox, free port are used in a table showing services. If user check the checkbox, free ports are used but then cancel the dialog either by pressing Esc or close the dialog, the state of checkbox is cached. If then user opens a dialog again checkbox is not checked but dialog is behaving like it is, because there are used free ports for port forwading. It forces user to check checkbox again, it finds another free ports and then uncheck it to get to default state.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21123) Port forwarding: Free ports for port forwarding are cached even though dialog was canceled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21123?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21123:
-------------------------------------
Labels: openshift_v3 port_forwarding_wizard (was: port_forwarding_wizard)
> Port forwarding: Free ports for port forwarding are cached even though dialog was canceled
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21123
> URL: https://issues.jboss.org/browse/JBIDE-21123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: openshift_v3, port_forwarding_wizard
>
> In Port forwarding dialog there is a checkbox to use free ports for port forwading. Upon checking this checkbox, free port are used in a table showing services. If user check the checkbox, free ports are used but then cancel the dialog either by pressing Esc or close the dialog, the state of checkbox is cached. If then user opens a dialog again checkbox is not checked but dialog is behaving like it is, because there are used free ports for port forwading. It forces user to check checkbox again, it finds another free ports and then uncheck it to get to default state.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21122) Port Forwarding: Start All button should be disabled if port forwarding is already active
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21122?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21122:
-------------------------------------
Labels: openshift_v3 (was: )
> Port Forwarding: Start All button should be disabled if port forwarding is already active
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-21122
> URL: https://issues.jboss.org/browse/JBIDE-21122
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.3.1.Beta1
>
>
> In Port Forwarding wizard is a button "Start All" which starts port forwarding for all services listed in a table. If user triggers the button and port forwarding is already active, Start All is still enabled and user can click on it again and again but nothing happens. Accessibility of this button should be similar as Stop All, which works as expected - if port forwarding is not active, it is disabled, otherwise it is enabled.
> There is also a checkbox to find free ports for port forwarding. Once port forwarding is active, checking and unchecking this checkbox do nothing. It should have same accessibility as Start All button - if there is active port forwarding, the checkbox should be disabled, otherwise it should be enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months