November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20900. ------------------------------ Resolution: Done Fixed in 4.3.x and 4.4.x: https://github.com/jbosstools/jbosstools-build-ci/commit/3734dce1a5240c56... https://github.com/jbosstools/jbosstools-build-ci/commit/fc3cdaae07cb8bcb... 72 jobs updated: https://github.com/jbdevstudio/jbdevstudio-ci/commit/c82c0d726d9d8f0f7eb1... new 4.3.1.Beta1-SNAPSHOT and 4.4.0.Alpha1-SNAPSHOT versions of org.jboss.tools.releng:jbosstools-releng-publish published here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... cc: [~pleacu] I've also updated a few JBTIS jobs: DevStudio/view/SOATooling/job/JBTIS-aggregate-publish/config.xml DevStudio/view/SOATooling/job/SwitchYard-Tools/config.xml Not sure if you have other jobs which rely on either of htese nexu artifacts: * org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip or * org.jboss.tools.releng:jbosstools-releng-publish:4.4.0.Alpha1-SNAPSHOT:zip But I'm hoping not. Please reopen if I missed any jobs that DO use those artifacts (rather than just using rsync.sh itself directly from github or nexus. > 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: Nick Boldt > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-21144) Invalid local template path validation is not shown correctly

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21144?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21144. --------------------------------- Thanks. This is resolved in latest nightly build of 4.3.1.Beta1 v20151127-0343-B91 . Closing. > Invalid local template path validation is not shown correctly > ------------------------------------------------------------- > > Key: JBIDE-21144 > URL: https://issues.jboss.org/browse/JBIDE-21144 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: invalid_value_local_template_tab.png, invalid_value_server_template_tab.png > > > In New OpenShift Application wizard on first wizard page where selection of a template is, there are two tabs, one for server and one for local template validation. If I put an invalid path to local template by typing/pasting value into text widget for local template path > !invalid_value_local_template_tab.png! > the path is not validated until I select server template tab. Then there is shown an error on the wizard page > !invalid_value_server_template_tab.png! > We should at least validate path to its existence and shown appropriate validation error mark on the first wizard page while local template tab is active. Processing of template is good as it is (it is processed after clicking next button), only validation need refining. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21148) Unhandled loop event exception is thrown if local template file path contains invalid value

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21148: ------------------------------------- Summary: Unhandled loop event exception is thrown if local template file path contains invalid value Key: JBIDE-21148 URL: https://issues.jboss.org/browse/JBIDE-21148 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda In New OpenShift Application wizard while Local template tab is selected on first wizard page and if in text widget for a file is invalid value, click on a File system... button throws following exception and nothing happens: {code} java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage$14.createFileDialog(TemplateListPage.java:712) at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage$14.widgetSelected(TemplateListPage.java:702) 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.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:279) at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:37) 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:497) 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: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} I expect value should be ignored and file browser dialog should be opened to allow user choose template. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21144) Invalid local template path validation is not shown correctly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21144?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21144: ------------------------------------- I believe the lack of recent build is caused by JBIDE-21145. In the mean time you can try http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > Invalid local template path validation is not shown correctly > ------------------------------------------------------------- > > Key: JBIDE-21144 > URL: https://issues.jboss.org/browse/JBIDE-21144 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: invalid_value_local_template_tab.png, invalid_value_server_template_tab.png > > > In New OpenShift Application wizard on first wizard page where selection of a template is, there are two tabs, one for server and one for local template validation. If I put an invalid path to local template by typing/pasting value into text widget for local template path > !invalid_value_local_template_tab.png! > the path is not validated until I select server template tab. Then there is shown an error on the wizard page > !invalid_value_server_template_tab.png! > We should at least validate path to its existence and shown appropriate validation error mark on the first wizard page while local template tab is active. Processing of template is good as it is (it is processed after clicking next button), only validation need refining. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21146) Provide search bar for an image in Deploy Image to OpenShift wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21146?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21146. --------------------------------- Resolution: Duplicate Issue Duplicate of JBIDE-20530 > Provide search bar for an image in Deploy Image to OpenShift wizard > ------------------------------------------------------------------- > > Key: JBIDE-21146 > URL: https://issues.jboss.org/browse/JBIDE-21146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Critical > Labels: docker > > There is no other way than remembering specific docker image to use in Deploy Image to OpenShift wizard and it is quite a pain. There could be some search bar as it is in docker pull image wizard to find desired image or a button which would open dialog to search for an image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3563) bad links in https://devstudio.redhat.com/updates/8.0/integration-stack/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3563?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3563. ---------------------------- Fix Version/s: 8.1.0.GA Assignee: Nick Boldt Resolution: Done Links fixed. Sorry about that! https://github.com/jbdevstudio/jbdevstudio-website/commit/2c105413d85020c... > bad links in https://devstudio.redhat.com/updates/8.0/integration-stack/ > ------------------------------------------------------------------------ > > Key: JBDS-3563 > URL: https://issues.jboss.org/browse/JBDS-3563 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 8.1.0.GA > > > https://devstudio.redhat.com/updates/8.0/integration-stack/ links to https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.1.0.GA-target... which does not exist. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21145) Component-install job is not reliable

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-21145: ------------------------------- Priority: Blocker (was: Major) > Component-install job is not reliable > ------------------------------------- > > Key: JBIDE-21145 > URL: https://issues.jboss.org/browse/JBIDE-21145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > We have often seen old artifacts on nightly sites (mars and neon too). It seems that the composite-install job is not reliable. The build is not triggered automatically with every new change in the repository. > Please investigate. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21145) Component-install job is not reliable

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-21145: ------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Component-install job is not reliable > ------------------------------------- > > Key: JBIDE-21145 > URL: https://issues.jboss.org/browse/JBIDE-21145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > We have often seen old artifacts on nightly sites (mars and neon too). It seems that the composite-install job is not reliable. The build is not triggered automatically with every new change in the repository. > Please investigate. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21145) Component-install job is not reliable

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-21145: ------------------------------------ This one [1] is from 2015-11-24 - which is 3 days old. Seems to be broken too. [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > Component-install job is not reliable > ------------------------------------- > > Key: JBIDE-21145 > URL: https://issues.jboss.org/browse/JBIDE-21145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Pavol Srna > > We have often seen old artifacts on nightly sites (mars and neon too). It seems that the composite-install job is not reliable. The build is not triggered automatically with every new change in the repository. > Please investigate. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21144) Invalid local template path validation is not shown correctly

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21144?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21144: --------------------------------------- There is no nightly build since Monday, so I was not able to test it with latest nightly. I will try it once there will be nightly build available. > Invalid local template path validation is not shown correctly > ------------------------------------------------------------- > > Key: JBIDE-21144 > URL: https://issues.jboss.org/browse/JBIDE-21144 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: invalid_value_local_template_tab.png, invalid_value_server_template_tab.png > > > In New OpenShift Application wizard on first wizard page where selection of a template is, there are two tabs, one for server and one for local template validation. If I put an invalid path to local template by typing/pasting value into text widget for local template path > !invalid_value_local_template_tab.png! > the path is not validated until I select server template tab. Then there is shown an error on the wizard page > !invalid_value_server_template_tab.png! > We should at least validate path to its existence and shown appropriate validation error mark on the first wizard page while local template tab is active. Processing of template is good as it is (it is processed after clicking next button), only validation need refining. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2015