November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16131) Create new _42 jobs and reconfigure _master to use Luna, not Kepler

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16131?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16131: ------------------------------- Description: Need to spawn copies of the _master jobs which will build from the jbosstools-4.2.* branches which we'll create for each code freeze. Need to also update the _master jobs to build w/ Luna, not Kepler. And we need a new Jenkins view to house the new jobs. See also https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... was: Need to spawn copies of the _master jobs which will build from the jbosstools-4.2.* branches which we'll create for each code freeze. Need to also update the _master jobs to build w/ Luna, not Kepler. And we need a new Jenkins view to house the new jobs. > Create new _42 jobs and reconfigure _master to use Luna, not Kepler > ------------------------------------------------------------------- > > Key: JBIDE-16131 > URL: https://issues.jboss.org/browse/JBIDE-16131 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Alpha1 > > > Need to spawn copies of the _master jobs which will build from the jbosstools-4.2.* branches which we'll create for each code freeze. > Need to also update the _master jobs to build w/ Luna, not Kepler. > And we need a new Jenkins view to house the new jobs. > See also https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16131) Create new _42 jobs and reconfigure _master to use Luna, not Kepler

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16131?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16131: ------------------------------- Priority: Blocker (was: Major) > Create new _42 jobs and reconfigure _master to use Luna, not Kepler > ------------------------------------------------------------------- > > Key: JBIDE-16131 > URL: https://issues.jboss.org/browse/JBIDE-16131 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > > Need to spawn copies of the _master jobs which will build from the jbosstools-4.2.* branches which we'll create for each code freeze. > Need to also update the _master jobs to build w/ Luna, not Kepler. > And we need a new Jenkins view to house the new jobs. > See also https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16131) Create new _42 jobs and reconfigure _master to use Luna, not Kepler

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16131: ---------------------------------- Summary: Create new _42 jobs and reconfigure _master to use Luna, not Kepler Key: JBIDE-16131 URL: https://issues.jboss.org/browse/JBIDE-16131 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Affects Versions: 4.2.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.2.0.Alpha1 Need to spawn copies of the _master jobs which will build from the jbosstools-4.2.* branches which we'll create for each code freeze. Need to also update the _master jobs to build w/ Luna, not Kepler. And we need a new Jenkins view to house the new jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16128: ---------------------------------------- The whole purpose of relying to Nexus is to reduce the amount of maintainance/gouvernance we have when it comes to publishing stuff. If we can rely on standard Maven mechanism, we provide more portability, with less effort. > If you're not going to consume the sites, when why bother? How will you know what the performance pros/cons are if we don't stress-test the system? The goal is first to see the issues that we'll have at publication (such as colliding versions). It's a first step. Ultimately, we'll also try to consume these Nexus site for aggregation. > Is the point of this to publish just milestones and .Final bits? Or every single nightly build? If the former, that's semi-reasonable, especially if we are planning to move toward the IS model of "components can release their Final earlier than the rest of the stack". Point is to publish SNAPSHOTs in a first time, through the CI jobs. Just that will require projects to start working on releasing their own "Final" as dealing with version is a necessary step in that direction. > Thus instead of these sites: ... we'd have the equivalent bits in Nexus: .... Nexus URLs are a bit ugly, that probably won't be the one we'll provide to end-users. If we go for a "build-on-nexus" approach, we'll probably release stuff by mirroring the output of Nexus to a nicer location, such as the ones we're using now. > What exactly does moving to nexus get us? Remove necessity to maintain: * publish.sh * URL conventions and many stuff related to publication of CI builds > Also, are you assuming that component owners will be responsible for doing their own promotes from nexus-staging to nexus-public? First, I would test it only for SNAPSHOTs. Component developers will learn that they need to take care of not having the same version on different streams. That would already be a great step forward. Then we may be interested in teaching them how to release their own component, but I see that as a secondary step, after simply publishing of SNAPSHOTs on Nexus. > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16128 > URL: https://issues.jboss.org/browse/JBIDE-16128 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha1 > > > In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus. > Then we'll see what are the pros/cons of this approach. > Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15313) Investigate how to handle Wildfly port multiplexing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15313?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15313: ------------------------------------- Some links on teh topic: https://community.jboss.org/wiki/CLIConnections-AddressHandling http://wildfly-development.1055759.n5.nabble.com/wildfly-dev-Change-CLI-t... > Investigate how to handle Wildfly port multiplexing > ---------------------------------------------------- > > Key: JBIDE-15313 > URL: https://issues.jboss.org/browse/JBIDE-15313 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen. > This jira will investigate what's necessary and what may need to change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16101) Broken layout of feature description with "Technology Preview" text on Fedora

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16101?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16101: ------------------------------------ cc: [~fbricon] [~maxandersen] [~burrsutter] [~mmurray] [~ldimaggio] [~mmusaji] Maybe the label text should be "Preview" instead of "Tech Preview?" > Broken layout of feature description with "Technology Preview" text on Fedora > ----------------------------------------------------------------------------- > > Key: JBIDE-16101 > URL: https://issues.jboss.org/browse/JBIDE-16101 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.CR1 > Environment: Fedora 18 64bit KDE, JBDS7.1.0.CR1 CR1-v20131124-0717-B560 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/devstudio-directory.xml > -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/ > Reporter: Vlado Pakan > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.2.x > > Attachments: jbide16101-not-sure-if-better.png, technologypreview.png > > > Instead of link with text "Technology Preview" only link with text "Technology" is displayed within Central as patr of JBoss Hybrid Mobile Mobile Tools + CordovaSim item in JBoss Central. > !technologypreview.png! > It's displayed correctly on OSX. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16101) Broken layout of feature description with "Technology Preview" text on Fedora

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16101?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16101: ------------------------------- Attachment: jbide16101-not-sure-if-better.png Here's what I see when I build this locally and fire it up in JBDS: !jbide16101-not-sure-if-better.png! Because the layout is always skewed on my machine, I can't be sure if the wrapping is happening or not. We can build this and see, or someone w/ another OS can apply the above PRs and build it locally [1] to verify if it looks correct. [1] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.1.1.... > Broken layout of feature description with "Technology Preview" text on Fedora > ----------------------------------------------------------------------------- > > Key: JBIDE-16101 > URL: https://issues.jboss.org/browse/JBIDE-16101 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.CR1 > Environment: Fedora 18 64bit KDE, JBDS7.1.0.CR1 CR1-v20131124-0717-B560 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/devstudio-directory.xml > -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/ > Reporter: Vlado Pakan > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.2.x > > Attachments: jbide16101-not-sure-if-better.png, technologypreview.png > > > Instead of link with text "Technology Preview" only link with text "Technology" is displayed within Central as patr of JBoss Hybrid Mobile Mobile Tools + CordovaSim item in JBoss Central. > !technologypreview.png! > It's displayed correctly on OSX. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16032) java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-16032: ----------------------------------- [~psrna] Are you sure about this? AFAICS the fix *is* included in 4.1.1.CR1a. I have verified the git log and tested with the 4.1.1.CR1a update site and I cannot reproduce the problem anymore. > java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences > --------------------------------------------------------------------- > > Key: JBIDE-16032 > URL: https://issues.jboss.org/browse/JBIDE-16032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-preferences.png > > > Stacktrace: > {code} > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$6.run(ForgeInstallationsPreferencePage.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.performOk(ForgeInstallationsPreferencePage.java:290) > at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) > at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171) > at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) > 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.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16130) Openshift Enterprise: Creating (separate) jenkins application invoked by adding jenkins client to other application does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16130?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-16130: ---------------------------------- Summary: Openshift Enterprise: Creating (separate) jenkins application invoked by adding jenkins client to other application does not work (was: Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work) > Openshift Enterprise: Creating (separate) jenkins application invoked by adding jenkins client to other application does not work > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16130 > URL: https://issues.jboss.org/browse/JBIDE-16130 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Attachments: jenkins.png > > > Steps to reproduce: > ASSERT: Have OpenShift Enterprise connection > ASSERT: Don't have Jenkins application on the given connection > EXEC: Open wizard for new application > EXEC: Choose some application type (doesn't matter which one) > EXEC: Toggle checkbox next to jenkins cartridge > EXEC: Click on "Apply" button > When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size. > !jenkins.png! > Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2686) Investigate use of SpringSource's Quick Search in JBT/JBDS Central

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2686?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-2686: -------------------------------- Assignee: Nick Boldt (was: Marián Labuda) > Investigate use of SpringSource's Quick Search in JBT/JBDS Central > ------------------------------------------------------------------ > > Key: JBDS-2686 > URL: https://issues.jboss.org/browse/JBDS-2686 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery, requirements, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.Alpha1 > > > @fbricon wrote: > {quote} > This looks very interesting > http://blog.springsource.org/2013/07/11/eclipse-quick-search/ > And it -apparently- doesn't depend on other spring stuff, so I > think it's a good candidate for integration in JBT/JBDS. > {quote} > Update site: > http://dist.springsource.com/release/TOOLS/eclipse-integration-commons/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2013