May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19839) Cannot proceed to New OpenShift Application wizard via shell menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19839?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19839: ------------------------------------- Sprint: Sprint #4 May 2015 > Cannot proceed to New OpenShift Application wizard via shell menu > ----------------------------------------------------------------- > > Key: JBIDE-19839 > URL: https://issues.jboss.org/browse/JBIDE-19839 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > Attachments: file-new-no_openshift.png, file-new-other-openshift.png, new-application-wizard-via-file-new.png > > > While trying to open a New OpenShift Application wizard via shell menu (File -> New -> OpenShift Application) it is not possible to get behind connection dialog. At first connection dialog is opened to chose desired connection where to create a new OpenShift application. After filling details and hitting the Finish button, New OpenShift Application should be opened. Issue is that it is not possible to click Finish button at all, because it is disabled all the time (grayed). > Same thing is in Central. Opening New OpenShift Application wizard via hyperlink in Central blocks user to proceed through connection dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19845) Creating a new OpenShift application via Configure context menu of a project always use first connection from OpenShift Explorer view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19845?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19845: ------------------------------------- Sprint: Sprint #4 May 2015 > Creating a new OpenShift application via Configure context menu of a project always use first connection from OpenShift Explorer view > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19845 > URL: https://issues.jboss.org/browse/JBIDE-19845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > > If user wants to create a new OpenShift application via context menu of a project, it is possible to do it via context menu "Configure - New/Import OpenShift application". Previously this selection prompted user to choose desired connection where to create a new application. Nowadays the first existing connection in OpenShift explorer view is selected and it is not possible to change connection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19880) Explorer: Unfolding v3 resources endlessly loads and stops me from unfolding any other resource-cathegory

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19880?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19880: ------------------------------------- Sprint: Sprint #4 May 2015 > Explorer: Unfolding v3 resources endlessly loads and stops me from unfolding any other resource-cathegory > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19880 > URL: https://issues.jboss.org/browse/JBIDE-19880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: explorer, v3 > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-expand-tree.mov, endless-loading-loop.ogv, endlessly-restarting-loading-job.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19711 at 5/27/15 3:19 PM: ------------------------------------------------------------- It's in -SR1- RC1. The plugins are also in M7... the problem is the API changed a lot over the past few weeks, so the code I have does not work with what's in M7. was (Author: rob.stryker): It's in SR1. The plugins are also in M7... the problem is the API changed a lot over the past few weeks, so the code I have does not work with what's in M7. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19711: --------------------------------------------- Rob, SR1 is being released in september or so - did you mean RC1 ? > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-276) Seeing problems creating a new SwitchYard project - Related to: https://issues.jboss.org/browse/JBTIS-275

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-276?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-276. ------------------------------ Resolution: Out of Date Resolving as out-of-date. Double checked creating a SwitchYard project in the 8.0.1 environment and all is well. > Seeing problems creating a new SwitchYard project - Related to: https://issues.jboss.org/browse/JBTIS-275 > --------------------------------------------------------------------------------------------------------- > > Key: JBTIS-276 > URL: https://issues.jboss.org/browse/JBTIS-276 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: switchyard > Affects Versions: 7.0.1.GA-JBDSIS > Environment: * eclipse-standard-kepler-SR2-Java8-linux-gtk-x86_64.tar.gz > * JBoss Tools from MarketPlace > * SwitchYard tools from http://download.jboss.org/jbosstools/updates/development/kepler/integrati... > * SwitchYard tools update from http://download.jboss.org/jbosstools/updates/development/kepler/integrati... > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 8.0.0.Beta1 > > Attachments: settings.xml > > > Seeing problems creating a new SwitchYard project - Related to: https://issues.jboss.org/browse/JBTIS-275: > With this Installed: > * eclipse-standard-kepler-SR2-Java8-linux-gtk-x86_64.tar.gz > * JBoss Tools from MarketPlace > * SwitchYard tools from http://download.jboss.org/jbosstools/updates/development/kepler/integrati... > * SwitchYard tools update from http://download.jboss.org/jbosstools/updates/development/kepler/integrati... > Path 1 > * With a FSW 6.0 runtime defined, and a totally empty maven repo, what should the user see for options when creating a new SwitchYard project? > * The defaults presented to the user are: > -> Configuration Version = 1.1 > -> Target Version = the defined FSW 6.0 runtime > -> Library Version = 1.1.1-p5-redhat-1 (greyed out) > Creating a new SwitchYard project raises this error: > * The container 'Maven Dependencies' references non existing library '/home/ldimaggi/.m2/repository/org/switchyard/switchyard-api/1.1.1-p5-redhat-1/switchyard-api-1.1.1-p5-redhat-1.jar' > Path 2 > * With zero server runtimes defined, and a totally empty maven repo, what should the user see for options when creating a new SwitchYard project? > * The defaults presented to the user are: > -> Configuration Version = 1.1 > -> Target Version = <none> > -> Library Version = 2.0.0-SNAPSHOT > Creating a new SwitchYard project raises this error: > * Could not find artifact org.switchyard:switchyard-plugin:pom:2.0.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18837: ------------------------------------ https://issues.jboss.org/browse/JBIDE-18837?focusedCommentId=13024507&pag... {quote}If you build the o.j.t.foundation.core plugin, as I did here passing in -DBUILD_ALIAS=foo, you will see in the currentversion.properties that the variables are correctly expanded. {quote} The test is that the BUILD_ALIAS you pass in via commandline (or via Jenkins job) appears correctly in the jar's currentversion.properties file, instead of the unexploded $\{jbosstools.version}. > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: generated-vs-soource-zip.png > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19830) Nullpointer at recieving schema

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19830?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-19830: --------------------------------- Assignee: Koen Aers > Nullpointer at recieving schema > ------------------------------- > > Key: JBIDE-19830 > URL: https://issues.jboss.org/browse/JBIDE-19830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.Alpha2 > Environment: Hibernate: 5.0.0.Alpha2-v20150417-1452-B12 > Eclipse: Eclipse Mars M7 > OS: Windows 7 x64 Enterprise > DB: Postgres 9.3 > Reporter: Philipp Birkl > Assignee: Koen Aers > > While receiving a schema from Database initially a _java.lang.NullPointerException* is thrown_. > !http://i.imgur.com/2Frtlwu.png! > Stack trace can be found [here|https://gist.github.com/calaedo/394f3fdb8994741de3ce#file-jbide-1983...]. > While debugging the plugin i found the problem at the implementation of the anonymous comperator in _org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(Object, IProgressMonitor)_. > {code} > res = toArray(result.iterator(), Object.class, new Comparator<Object>() { > public int compare(Object arg0, Object arg1) { > return getName(arg0).compareTo(getName(arg1)); > } > private String getName(Object o) { > String result = null; > try { > Method m = o.getClass().getMethod("getName", new Class[] {}); > m.invoke(o, new Object[] {}); > } catch (Exception e) { > throw new RuntimeException(e); > } > return result; > } > }); > {code} > The string result is never set. So the _compareTo_ is always failing. > I haven't looked it up, but the problem might consist also in earlier versions of JBoss tools. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19711: ------------------------------------ We're actually targeting Mars RC2, as it's out today (EPP bundles tomorrow) so I'll start pulling mirrors ASAP and we should have something in a form that can be PR'd and p2diff'd tomorrow. Assuming we don't sit on our hands reviewing the PR too long, we should have it merged & built by Friday. [~rob.stryker] I'll let you know when there's a mirror against which you can build your stuff / review the upstream API changes. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19879 at 5/27/15 1:13 PM: ------------------------------------------------------------- All four requested plugins are here: http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... {quote} I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin.{quote} So therefore the PLUGIN names / ids are: {code} org.eclipse.launchbar.core_1.0.0.201505051901.jar org.eclipse.launchbar.ui_1.0.0.201505051901.jar org.eclipse.remote.core_2.0.0.201505042103.jar org.eclipse.remote.ui_2.0.0.201505042103.jar {code} Which becomes, in a PR: {code} <unit id="org.eclipse.launchbar.core" version="1.0.0.201505051901"/> <unit id="org.eclipse.launchbar.ui" version="1.0.0.201505051901"/> <unit id="org.eclipse.remote.core" version="2.0.0.201505042103"/> <unit id="org.eclipse.remote.ui" version="2.0.0.201505042103"/>{code} ¿Muy fácil, no? was (Author: nickboldt): All four requested plugins are here: http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... > Add o.e.remote and o.e.launchbar to TP > -------------------------------------- > > Key: JBIDE-19879 > URL: https://issues.jboss.org/browse/JBIDE-19879 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, target-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Rob Stryker > Assignee: Nick Boldt > > *Reason:* JBIDE-19711 - WTP servertools integration with CDT launchbar > *Project page/sources:* ... Requires dependencies on CDT and Launchbar. Launchbar is in http://www.eclipse.org/cdt/ and o.e.remote is in http://www.eclipse.org/ptp/ > *Version:* - Required launchbar is 1.0.0 found in MASTER at their repository. There is no released version yet with the stable API required. Required o.e.remote version is 2.0.0 in MASTER at their repository. There is no released version yet with the stable API required. > *License and owner:* ... Both are eclipse projects licensed under EPL > *Original p2 repo:* I am unable to locate the original update sites / p2 repos. PTP does not seem to have an update site URL to the best of my searching (http://download.eclipse.org/tools/ptp/builds/9.0.0/ does not list an update site url, but does have a zip containing an update site). CDT does not list update sites for mars at https://eclipse.org/cdt/downloads.php > *JBoss mirror:* - Not sure what's applicable here. http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... does have all plugins needed, but none are the API required, as we require the code from Master. > *Include Sources: - It's always nice to include sources for devs who build tp locally with the fetch-sources flag ;) > *Affected projects: - jbosstools-server > *Include in JBDS:* - No, for now. > *Type of dependency:* distribution > *List of bundles added/removed:* - At this time, I expect to require org.eclipse.launchbar.core, org.eclipse.launchbar.ui, org.eclipse.remote.core, org.eclipse.remote.ui. > Unfortunately I'm unable to test if this is sufficient, at the moment. There may be other plugins that are transient deps somehow that I'm not seeing since I don't have a TP to build against that works. > If applicable: > *non-p2 repository:* ??? > *non-p2 ids:* ??? > Suggested Patch for TP: - At this point, I have no suggested patch. I do not know how to add a dependency on nightly builds for these two blocks of code. Also, I'm a bit confused why http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... will list a plugin (for example org.eclipse.cdt.core.native_5.8.0.201505050312.jar) but the .target file references a feature group (?) which is not present in the requirements/mars folder, such as <unit id="org.eclipse.cdt.native.feature.group" version="8.7.0.201505050312"/> > I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin. Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group > So I'm not sure how you're converting a required plugin id to a feature group. The devdoc also provides no assistance in this matter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

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 May 2015