July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22814) ResourceException below HibernateProjectConfigurator.configureInternal (thrown in Project.checkAccessible)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22814?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-22814. --------------------------------- Resolution: Done It appears the bug occurs while the project being updated has been closed (so very hard to reproduce). Fix consists in checking if project is accessible. > ResourceException below HibernateProjectConfigurator.configureInternal (thrown in Project.checkAccessible) > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22814 > URL: https://issues.jboss.org/browse/JBIDE-22814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Fred Bricon > Fix For: 4.4.1.AM3 > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > org.eclipse.core.internal.resources.ResourceException: HIDDEN > at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:143) > at org.eclipse.core.internal.resources.Project.hasNature(Project.java:521) > at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.configureInternal(HibernateProjectConfigurator.java:53) > at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.mavenProjectChanged(HibernateProjectConfigurator.java:90) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:919) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:98) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:81) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jst.j2ee.ejb.annotations.xdoclet | 1.2.200.v201103302126 | 1.2.200.v201103302126 | > | org.eclipse.m2e.core | 1.6.2.20150902-0002 | 1.7.0.20160603-1933 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.maven.hibernate | 1.7.1.Final-v20160401-1059-B103 | 1.8.0.Final-v20160613-2000-B8 | > Operating Systems: > | Linux | 3.10.0.18 | 4.4.0 | > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5720f424e4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-816) Cannot install SwitchYard tooling from EA zip file in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-816?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-816: ----------------------------------------- Hi [~pleacu], if you plan to include the missing dependencies into JBDS-IS 9.0.1.GA-earlyaccess then I prefer to have the respin as soon as possible. > Cannot install SwitchYard tooling from EA zip file in offline mode > ------------------------------------------------------------------ > > Key: JBTIS-816 > URL: https://issues.jboss.org/browse/JBTIS-816 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.CR3 > Environment: JBDS 9.1.0.GA + devstudio-integration-stack-9.0.1.CR3-earlyaccess.zip > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Cannot install SwitchYard tooling from EA zip file in offline mode due to missing > * org.eclipse.zest.core 1.5.100 (required by fuse tooling) > * org.eclipse.emf.compare.feature.group 2.1.0 (required by switchayrd tooling) > * org.eclipse.bpel.feature.feature.group [1.0.2,2.0.0) (required by switchyard bpel tooling) > All features mentioned above are available in devstudio-integration-stack-9.0.1.CR3.zip. So, to install all features in offline mode we need both zip files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-816) Cannot install SwitchYard tooling from EA zip file in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-816?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-816: ---------------------------------- This all happened because we were originally going to only change TD for this release. When we added Fuse/SY back in that caused the 4.3.2.Final TP to be invalid (although it *is* valid for JBDSIS 9.0.2). So - I've been adding the dependencies back in. This should do it (the remaining differences appear to be clearly Teiid Des related). I'm respining the 4.3.2-SNAPSHOT target platform (we'll go with that TP for this release given that 9.0.2 is coming soon after).. Do you want a quick respin of CR3? - no difference other than adding some TP dependencies back into EA. Otherwise I'll pick them up when I build .Final/.GA. > Cannot install SwitchYard tooling from EA zip file in offline mode > ------------------------------------------------------------------ > > Key: JBTIS-816 > URL: https://issues.jboss.org/browse/JBTIS-816 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.CR3 > Environment: JBDS 9.1.0.GA + devstudio-integration-stack-9.0.1.CR3-earlyaccess.zip > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Cannot install SwitchYard tooling from EA zip file in offline mode due to missing > * org.eclipse.zest.core 1.5.100 (required by fuse tooling) > * org.eclipse.emf.compare.feature.group 2.1.0 (required by switchayrd tooling) > * org.eclipse.bpel.feature.feature.group [1.0.2,2.0.0) (required by switchyard bpel tooling) > All features mentioned above are available in devstudio-integration-stack-9.0.1.CR3.zip. So, to install all features in offline mode we need both zip files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-360) Need to create launch shortcut for opening html files in chrome / chromium browser with debug port enabled [EBZ#497853]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-360: --------------------------------------- Summary: Need to create launch shortcut for opening html files in chrome / chromium browser with debug port enabled [EBZ#497853] Key: ERT-360 URL: https://issues.jboss.org/browse/ERT-360 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot In order to support front-end debugging via file protocol, need to create launch shortcut for opening html files in chrome / chromium browser with debug port enabled (--remote-debugging-port=9222) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22825) Forge New and Noteworthy for 4.4.1.AM2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22825?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22825: ----------------------------------------- I am on vacation until August 2nd. [~akazakov] can you work on this? I guess the Forge runtime upgrade is the only noteworthy feature > Forge New and Noteworthy for 4.4.1.AM2 > -------------------------------------- > > Key: JBIDE-22825 > URL: https://issues.jboss.org/browse/JBIDE-22825 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.1.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-358) Replace traces of old parser in Search/Indexing code. [EBZ#498371]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-358?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-358: ----------------------------- Story Points: 25 > Replace traces of old parser in Search/Indexing code. [EBZ#498371] > ------------------------------------------------------------------ > > Key: ERT-358 > URL: https://issues.jboss.org/browse/ERT-358 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: General, bzira > > Search and Indexing should be changed to use the newer dom ASTParser, instead of the old parser (e.g. in org.eclipse.wst.jsdt.internal.core.search.indexing.SourceIndexer). > This needs to happen before any other improvements/refinements to JSDT Search. > Looking at org.eclipse.wst.jsdt.internal.compiler.SourceElementParser, most of the class is using deprecated code. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22738) Image registry URL becomes null when going between Connection and Deploy pages on Deploy image to OS wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22738?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22738: ----------------------------------- Sprint: devex #117 July 2016, devex #118 July 2016 (was: devex #117 July 2016) > Image registry URL becomes null when going between Connection and Deploy pages on Deploy image to OS wizard > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22738 > URL: https://issues.jboss.org/browse/JBIDE-22738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitry Bocharov > Assignee: Dmitry Bocharov > Attachments: WAY1.webm, WAY2.webm > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3966) Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3966?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3966. ---------------------------------- Release Notes Text: Resolving because it's blocking the current sprint to be completed. The supertask is closed so all subtasks should be closed as well. Len please remove this subtask if you don't need it anymore. Resolution: Done > Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning > --------------------------------------------------------------------------------------------- > > Key: JBDS-3966 > URL: https://issues.jboss.org/browse/JBDS-3966 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: platform-installer > Reporter: Len DiMaggio > Fix For: 10.1.0.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3966) Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3966?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3966. -------------------------------- > Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning > --------------------------------------------------------------------------------------------- > > Key: JBDS-3966 > URL: https://issues.jboss.org/browse/JBDS-3966 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: platform-installer > Reporter: Len DiMaggio > Fix For: 10.1.0.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-359) Remove Log in Docker Explorer is not working [EBZ#497822]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-359: --------------------------------------- Summary: Remove Log in Docker Explorer is not working [EBZ#497822] Key: ERT-359 URL: https://issues.jboss.org/browse/ERT-359 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Steps to reproduce: 1. Run in console: docker run -d -p 5000:5000 -v /home/jkopriva/temp2/config1.yml:/etc/docker/registry/config.yml:rw --name registry11 registry:2 2. Connect with Docker Tooling to Docker instance. 3. Click on Display log on registry11 container 4. Log is displayed in console view. 5. Remove Log of registry11 container in Docker Explorer. 6. Run registry11. 7. Log is not deleted Docker version: Docker version 1.10.3, build 19b5791/1.10.3 Eclipse version: Eclipse Java EE IDE for Web Developers. Version: Neon Release (4.6.0) Build id: 20160613-1800 Docker Tooling version: 2.1.0.201607122122 System: Fedora 24 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016