December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23597) Integration tests global refactoring: org.jboss.tools.usercase.ticketmonster.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23597?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-23597. ------------------------------------ > Integration tests global refactoring: org.jboss.tools.usercase.ticketmonster.ui.bot.test > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23597 > URL: https://issues.jboss.org/browse/JBIDE-23597 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: integration, integration_tests, ticketmonster > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.usercase.ticketmonster.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22145: --------------------------------------- [~rob.stryker] what did we fix on our end? Any way to verify? > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: FSWatcherHang.txt, FailureWatchModify1.PML, FileWatchError.zip, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23381) foundation.checker is UI and should not be dep'd by foundation.core

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23381?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23381. --------------------------------- The commit seems ok. foundation.core no longer depends on foundation.checker. > foundation.checker is UI and should not be dep'd by foundation.core > ------------------------------------------------------------------- > > Key: JBIDE-23381 > URL: https://issues.jboss.org/browse/JBIDE-23381 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: foundation > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > The checker plugin has UI deps and should not be positioned below foundation.core. This pollutes our entire dependency tree. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23400) Test failure for foundation.help

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23400?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23400. --------------------------------- Tests have been passing since. Closing. > Test failure for foundation.help > -------------------------------- > > Key: JBIDE-23400 > URL: https://issues.jboss.org/browse/JBIDE-23400 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.4.2.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_maste... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4145) Drop dependency on "org.eclipse.core.runtime.compatibility.auth"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4145?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-4145. ------------------------------- All of the PRs were merged and things didn't break, so closing :) > Drop dependency on "org.eclipse.core.runtime.compatibility.auth" > ---------------------------------------------------------------- > > Key: JBDS-4145 > URL: https://issues.jboss.org/browse/JBDS-4145 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: 3rd-party-dependencies > Affects Versions: 10.2.0.AM2 > Reporter: Mat Booth > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.2.0.AM3 > > > For some reason JBDS feature has a requirement on "org.eclipse.core.runtime.compatibility.auth" bundle: > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > This bundle has not shipped with the Eclipse platform since version 4.2 in 2012 when it was obsoleted. The bundle was finally deleted from the upstream git repo in 2014: > http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?id... > Needless to say, if it was deleted from upstream git repo, it cannot be supported -- there is no chance to get bugfixes upstream here :-) > See the eclipse.org bug for more details: https://bugs.eclipse.org/bugs/show_bug.cgi?id=336129 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23559) Server New and Noteworthy for 4.4.2.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23559?page=com.atlassian.jira.plugi... ] Jeff MAURY resolved JBIDE-23559. -------------------------------- Resolution: Done > Server New and Noteworthy for 4.4.2.Final > ----------------------------------------------------- > > Key: JBIDE-23559 > URL: https://issues.jboss.org/browse/JBIDE-23559 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Server4.4.2.Final #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of Server, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23537) Create New and Noteworthy for 4.4.2.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23537?page=com.atlassian.jira.plugi... ] Jeff MAURY resolved JBIDE-23537. -------------------------------- Resolution: Done > Create New and Noteworthy for 4.4.2.Final > ----------------------------------------- > > Key: JBIDE-23537 > URL: https://issues.jboss.org/browse/JBIDE-23537 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.4.2.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-463) DockerException in DockerExplorerContentProvider$1.run [EBZ#508266]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-463?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-463. ------------------------------- Resolution: Done > DockerException in DockerExplorerContentProvider$1.run [EBZ#508266] > ------------------------------------------------------------------- > > Key: ERT-463 > URL: https://issues.jboss.org/browse/ERT-463 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon.1 (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon.2 (4.6) > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > org.eclipse.linuxtools.docker.core.DockerException: HIDDEN > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:186) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Bundles: > | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 | > | org.eclipse.linuxtools.docker.ui | 2.1.0.201611050402 | 2.1.0.201611050402 | > Operating Systems: > | Windows | 6.1.0 | 6.1.0 | > The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5836a... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. > Created on behalf of xcoulon(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4146. ------------------------------ Thanks you both, it works fine with rh-eclipse46-eclipse-epp-logging 2.0.3-1.2.el7. > Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4146 > URL: https://issues.jboss.org/browse/JBDS-4146 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, webservices > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.2.0.GA > > Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, eclipse-log-after-new-workspace.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt > > > As of the latest rpm build [1] I'm only getting this one error now: > {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075 > !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629 > !STACK 0 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-473) Don't try to browse a container that isn't using TTY [EBZ#508705]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-473: --------------------------------------- Summary: Don't try to browse a container that isn't using TTY [EBZ#508705] Key: ERT-473 URL: https://issues.jboss.org/browse/ERT-473 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.2 (4.6) The browse Container features of Copy from Container and Copy to Container features rely on using exec to run ls and gather info from the Container. This does not work reliably when the Container is not created with the tty option. Instead, treat the Container as if it was stopped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 December 2016