February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19175) Console configuration hibernate not found error when generating JPA Entities with disabled console setting

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19175?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19175: ------------------------------ Fix Version/s: 4.2.3.CR1 (was: 4.2.3.Beta1) > Console configuration hibernate not found error when generating JPA Entities with disabled console setting > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19175 > URL: https://issues.jboss.org/browse/JBIDE-19175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.2.Final > Environment: JBDS 8.0.2 GA, L64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.3.CR1, 4.3.0.Alpha2 > > > Console configuration hibernate not found error occurs when I try to generate entities without using hibernate console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18508) EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18508?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18508: ------------------------------------- So, the fix works as I intended : if you close/reopen just the ear project, all its dependencies will be reset/deployed properly. Now the problem is closing and reopening multiple projects at the same time : the ejb dependencies are not added as ear dependencies. Maybe a race condition here. I'll see if it's easily fixable. > EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening > ------------------------------------------------------------------------------------- > > Key: JBIDE-18508 > URL: https://issues.jboss.org/browse/JBIDE-18508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.1.2.Final > Reporter: Marek Schmidt > Assignee: Fred Bricon > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > Attachments: seam-restbay-src.zip > > > EAR Maven project loses lib/ artifacts deployed to EAP after closing/reopening > 0. setup the redhat techpreview/all maven repository > 1. Import the (attached) project as Maven project > 2. Deploy the restbay-ear project to EAP 6.2 (or 6.3) > 3. Close all 4 subprojects of the restbay project > 4. reopen all the restbay projects > 5. now the application will automatically redeploy > 6. this redeployment will result in a failure. > If you compare the deployment folders before/after the closing/reopening of the project, you will notice some of the restbay-ear.ear/lib/ libraries are missing. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-399) Cannot install JBDS-IS earlyaccess in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-399: ---------------------------------- [~nickboldt] Is this: 1. A duplicate of JBDS-3361 that will be fixed when it gets fixed? 2. A documentation issue - users must install the JBDS target platform zip separately? Just looking on how to handle this Jira. WDYT?? > Cannot install JBDS-IS earlyaccess in offline mode > -------------------------------------------------- > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Attachments: error.txt, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-400) JBDSIS 7.1.0 should be built with Kepler SR2, not SR1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-400?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-400. ------------------------------ Fix Version/s: 4.1.9.Final-TP (was: 4.1.1) Resolution: Done Eclipse Kepler SR2 picked up with 4.1.9.Final TP. > JBDSIS 7.1.0 should be built with Kepler SR2, not SR1 > ----------------------------------------------------- > > Key: JBTIS-400 > URL: https://issues.jboss.org/browse/JBTIS-400 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 4.1.1 > Reporter: Len DiMaggio > Assignee: Paul Leacu > Fix For: 4.1.9.Final-TP > > Attachments: p2diff710-SR2vsSR2a.txt > > > This issue was raised at the February 25 JBoss Tools build meeting. > The JBDSIS 7.1.0 release, which is based on Kepler, should be built on Kepler SR2, not SR1. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or shortly after startup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19376: ------------------------------------- The deadlock seems to occur during startup, when some plugins are first instantiated, and sticks around the whole time. As an initial workaround, as you mentioned, I'd suggest starting eclipse, closing your Servers view, closing eclipse, and re-starting it. This will likely stop the deadlock during initialization. As for a solution, well, I'll need to dig a bit deeper I guess. > Eclipse freezes at or shortly after startup > ------------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-3359: --------------------------------- Workaround Description: Update to JBDS 8.1 first Workaround: Workaround Exists > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3359: ----------------------------------------- Release Notes Docs Status: (was: Not Yet Documented) Assignee: Nick Boldt (was: Supriya Bharadwaj) Affects: Documentation (Ref Guide, User Guide, etc.),Release Notes > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3359: ----------------------------- Release Notes Docs Status: Not Yet Documented > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Jiri Pallich reassigned JBDS-3359: ---------------------------------- Assignee: Supriya Bharadwaj (was: Nick Boldt) > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Supriya Bharadwaj > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or shortly after startup

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19376: ------------------------------- Summary: Eclipse freezes at or shortly after startup (was: Eclipse freezes at or short after startup) > Eclipse freezes at or shortly after startup > ------------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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