January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-21) Update or replace JSDT parser to support ES6 [EBZ#481706]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-21?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-21: ---------------------------- Story Points: 75 > Update or replace JSDT parser to support ES6 [EBZ#481706] > --------------------------------------------------------- > > Key: ERT-21 > URL: https://issues.jboss.org/browse/ERT-21 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Support ecma-262 standard Javascript language features with the JSDT parser so that other functionality can provide relevant support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-36) Disable TypeBinding and deprecate internal ast model [EBZ#484598]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-36?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-36: ---------------------------- Story Points: 2 > Disable TypeBinding and deprecate internal ast model [EBZ#484598] > ----------------------------------------------------------------- > > Key: ERT-36 > URL: https://issues.jboss.org/browse/ERT-36 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M5, General, bzira > Fix For: Neon (4.6) M5 > > > Disable type binding to allow the replacement for a new Parser. > maintaining 2 ast models is wasteful deprecate org.eclipse.wst.jsdt.internal.compiler.ast model in favor of dom ast model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21590: ----------------------------------------------- [~jcantrill], yes the changes are essential and should be taken into account. However, for this issue, it is about project deleted by user action, OpenShiftJobs.createDeleteProjectJob() runs a job that requests delete of project on server and then fires event projects changed, with new list without the project. Explorer content provider listens to the event and has to remove project from children of connection node. It should work, but according to this issue does not. As much as I can see, changes to JBIDE-21457 do not affect that part. If you can reproduce this issue, could you try implement equals() and hashCode() for OpenShiftProjectUIModel and check if it helps. > Explorer: OpenShift connection is not refreshed upon project deletion > --------------------------------------------------------------------- > > Key: JBIDE-21590 > URL: https://issues.jboss.org/browse/JBIDE-21590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > > Upon deletion of a project under a connection in OpenShift explorer view, the deleted project is still visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21590: --------------------------------------- Project will always need to be manually refreshed if they are deleted servers-side; we can only properly handle cases where we delete the from the client side. Unlike the other resource where the watch is per project, there is not a callback mechanism for project changes unless you watch on the default namespace. This requires you to be a cluster admin which we can not guarantee. In regards to the other points brought up, there may well be some memory leaks with regards to things we cache; they should probably be investigated in more detail. Caching of project may no longer be necessary with some of the existing changes because the adapter classes now keep reference to their parent. This should allow us to properly refresh trees without having to figure out the parent. > Explorer: OpenShift connection is not refreshed upon project deletion > --------------------------------------------------------------------- > > Key: JBIDE-21590 > URL: https://issues.jboss.org/browse/JBIDE-21590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > > Upon deletion of a project under a connection in OpenShift explorer view, the deleted project is still visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-21363: ------------------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > create bugzilla importer for JIRA > --------------------------------- > > Key: JBIDE-21363 > URL: https://issues.jboss.org/browse/JBIDE-21363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.4.0.Alpha1 > > > Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA. > This scraper would: > * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues) > * [REQ2] generate a JIRA for each one found (no dupes should be created) > * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug # > * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. > * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript > * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT > * [REQ7] run as a Jenkins job every 3 hours > Generated JIRA example: > {code} > title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] > issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535 > description: (scraped from BZ comment #0) > affectsversion: (scraped from BZ version 1.6.0) > fixversion: (scraped from BZ target milestone ---) > component: (scraped from product:component = m2e:ui) > labels: RHT, ERT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21363 at 1/29/16 4:34 PM: ------------------------------------------------------------- ERT JIRAs are now live: https://issues.stage.jboss.org/browse/ERT Known issues: * not working: BZ closed duplicate -> JIRA closed dupe; workaround: close JIRA manually for now * fixversions don't include .y versions, eg., should have 4.5.2 instead of 4.5: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... * need component leads for Platform and WTP Incubator: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... * dryrun no longer works * query shown in console doesn't return the same number of results as its equivalent XMLRPC query, so it's meaningless to put it there; should show the equivalent buglist.cgi?chfieldfrom= query so the same range of issues are seen was (Author: nickboldt): ERT JIRAs are now live: https://issues.stage.jboss.org/browse/ERT Known issues: * not working: BZ closed duplicate -> JIRA closed dupe; workaround: close JIRA manually for now * fixversions don't include .y versions, eg., should have 4.5.2 instead of 4.5: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... * need component leads for Platform and WTP Incubator: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... > create bugzilla importer for JIRA > --------------------------------- > > Key: JBIDE-21363 > URL: https://issues.jboss.org/browse/JBIDE-21363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA. > This scraper would: > * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues) > * [REQ2] generate a JIRA for each one found (no dupes should be created) > * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug # > * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. > * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript > * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT > * [REQ7] run as a Jenkins job every 3 hours > Generated JIRA example: > {code} > title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] > issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535 > description: (scraped from BZ comment #0) > affectsversion: (scraped from BZ version 1.6.0) > fixversion: (scraped from BZ target milestone ---) > component: (scraped from product:component = m2e:ui) > labels: RHT, ERT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21601) p2director install should support excluding IUs like platform fragments and executables

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21601?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21601. ------------------------------ Resolution: Done > p2director install should support excluding IUs like platform fragments and executables > --------------------------------------------------------------------------------------- > > Key: JBIDE-21601 > URL: https://issues.jboss.org/browse/JBIDE-21601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > p2director install test should exclude things like executable.feature.group and org.eclipse.equinox.launcher.* > {code} > 01:27:34 [p2.dir] Cannot complete the install because of a conflicting dependency. > 01:27:34 [p2.dir] Software being installed: Eclipse Platform Launcher Executables 3.6.200.v20151113-1733 (org.eclipse.equinox.executable.feature.group 3.6.200.v20151113-1733) > 01:27:34 [p2.dir] Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151218-1543 (epp.package.jee 4.6.0.20151218-1543) > 01:27:34 [p2.dir] Only one of the following can be installed at once: > 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20151013-1129 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20151013-1129) > 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20160105-0945 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20160105-0945) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21590: ----------------------------------------------- I have noticed a couple of things that may not cause this issue but be related. OpenShiftExplorerContentProvider.getChildrenFor() for connection always creates and returns new instances of OpenShiftProjectUIModel together with new instance of DeploymentResourceMapper. If previous call for connection children already created such objects and they are in projectCache map, then they are just replaced and lost, but they are not disposed, mappper remains a listener to ConnectionsRegistry, and project adapter to mapper; so that it is a possible memory leak that also actively processes changes. Request for children certainly happens on action Refresh for connection. The adding/removing a connection causes complete content refresh so that project adapters for all projects of all connections will be recreated, leaving old objects lost but not disposed. (Note that method BaseExplorerContentProvider.handleConnectionRemoved() is never called now, it may be called from ConnectionsRegistryListener.connectionRemoved() or removed as dead code.) Now, closer to the issue. It seems possible that getChildrenFor() may be called twice, through launchLoadingJob() and directly by loadChildren() while loadedElements has stub. Then, projectCache may have the other set of project adapters for the connection than returned to viewer as children. If that might be the case, the rest is simple: handleProjectChanges() looks for project adapter by key (connection+project) and requests the viewer to remove it from parent connection node. But it is the wrong instance. Nevertheless, viewer still could remove it if OpenShiftProjectUIModel implemented hashCode() and equals() but it does not. [~jcantrill], could you please look into my guesses. I may have missed something of course. > Explorer: OpenShift connection is not refreshed upon project deletion > --------------------------------------------------------------------- > > Key: JBIDE-21590 > URL: https://issues.jboss.org/browse/JBIDE-21590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > > Upon deletion of a project under a connection in OpenShift explorer view, the deleted project is still visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20331) install grinder fails if blocked by Firefox

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20331: ------------------------------- Attachment: naginator-reschedules.png Now getting builds to reschedule when failing... result seems to be more blue balls: !naginator-reschedules.png! > install grinder fails if blocked by Firefox > ------------------------------------------- > > Key: JBIDE-20331 > URL: https://issues.jboss.org/browse/JBIDE-20331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: build-history.png, build-history2.png, build-history3.png, ff-profile-manager.png, install-grinder-bad-firefox.jpeg, install-grinder-fail.txt, install-grinder-firefox-problem-testInstall(org.jboss.tools.tests.installation.InstallTest).jpeg, naginator-reschedules.png, new-firefox-block-UI_dev112.png, new-firefox-block-UI_dev59.png, virt1-ftl.png, virt2-ftl.png > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull} > 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21601) p2director install should support excluding IUs like platform fragments and executables

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21601?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21601: ------------------------------------ Fixed in 4.3.x and 4.4.x: https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.4.x https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x Implemented in jobs: https://github.com/jbdevstudio/jbdevstudio-ci/commit/caec28ec8a50deeb6461... Upshot is that now we can use p2director to install all of Central/EA content into pre-release EPP bundles like https://hudson.eclipse.org/packaging/job/neon.epp-tycho-build/143/artifac... > p2director install should support excluding IUs like platform fragments and executables > --------------------------------------------------------------------------------------- > > Key: JBIDE-21601 > URL: https://issues.jboss.org/browse/JBIDE-21601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > p2director install test should exclude things like executable.feature.group and org.eclipse.equinox.launcher.* > {code} > 01:27:34 [p2.dir] Cannot complete the install because of a conflicting dependency. > 01:27:34 [p2.dir] Software being installed: Eclipse Platform Launcher Executables 3.6.200.v20151113-1733 (org.eclipse.equinox.executable.feature.group 3.6.200.v20151113-1733) > 01:27:34 [p2.dir] Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151218-1543 (epp.package.jee 4.6.0.20151218-1543) > 01:27:34 [p2.dir] Only one of the following can be installed at once: > 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20151013-1129 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20151013-1129) > 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20160105-0945 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20160105-0945) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2016