February 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3363) Remove Portlet tooling from default JBDS installation

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3363: -------------------------------- > Remove Portlet tooling from default JBDS installation > ----------------------------------------------------- > > Key: JBDS-3363 > URL: https://issues.jboss.org/browse/JBDS-3363 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, installer, requirements > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Portlet tools currently has a hard dependency on Seam, which kinda bothers us with JBDS-3286. > While severing this dependency is a WIP (JBIDE-19316), another question comes to mind : is portlet still necessary? > It doesn't seem like a technology we're trying to promote, tooling has been in maintenance mode for months if not years. Is it not time to [let it go|https://www.youtube.com/watch?v=moSFlvxnbgk&t=56s]? > > [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray], [~snjeza] : WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3363) Remove Portlet tooling from default JBDS installation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3363: ----------------------------- CDW release: + (was: ?) > Remove Portlet tooling from default JBDS installation > ----------------------------------------------------- > > Key: JBDS-3363 > URL: https://issues.jboss.org/browse/JBDS-3363 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, installer, requirements > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Portlet tools currently has a hard dependency on Seam, which kinda bothers us with JBDS-3286. > While severing this dependency is a WIP (JBIDE-19316), another question comes to mind : is portlet still necessary? > It doesn't seem like a technology we're trying to promote, tooling has been in maintenance mode for months if not years. Is it not time to [let it go|https://www.youtube.com/watch?v=moSFlvxnbgk&t=56s]? > > [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray], [~snjeza] : WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3364: ----------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/274, https://github.com/jbdevstudio/jbdevstudio-product/commit/d5ddd846138bd70... Fixed in master: https://github.com/jbdevstudio/jbdevstudio-product/commit/d5ddd846138bd70... PR applied in 4.2.x branch: https://github.com/jbdevstudio/jbdevstudio-product/pull/274 > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3364: ----------------------------- CDW devel_ack: + (was: ?) Status: New (was: New) > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19149) forge.core tests failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19149?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-19149. ------------------------------------ Resolution: Rejected The latest build was successful in Jenkins. Closing. > forge.core tests failure > ------------------------ > > Key: JBIDE-19149 > URL: https://issues.jboss.org/browse/JBIDE-19149 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.Beta1 > Reporter: Alexey Kazakov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.3.Beta1 > > > {code} > testGetDefaultInitialCase(org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest) Time elapsed: 0.002 sectestGetDefaultAndGetInstallationsAlternativeCase(org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest) Time elapsed: 0.008 sec <<< FAILURE! > java.lang.AssertionError: expected:<org.jboss.tools.forge.core.internal.runtime.ForgeEmbeddedRuntime@291bc55> but was:<null> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest.verifyEmbedded(ForgeRuntimesPreferencesTest.java:179) > at org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest.testGetDefaultAndGetInstallationsAlternativeCase(ForgeRuntimesPreferencesTest.java:163) > {code} > {code} > testForgeEmbeddedRuntime(org.jboss.tools.forge.core.process.ForgeEmbeddedRuntimeTest) Time elapsed: 0.001 sec <<< FAILURE! > org.junit.ComparisonFailure: expected:<1.[4.4].Final - embedded> but was:<1.[3.3].Final - embedded> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.jboss.tools.forge.core.process.ForgeEmbeddedRuntimeTest.testForgeEmbeddedRuntime(ForgeEmbeddedRuntimeTest.java:47) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19149) forge.core tests failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19149?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19149. ---------------------------------- > forge.core tests failure > ------------------------ > > Key: JBIDE-19149 > URL: https://issues.jboss.org/browse/JBIDE-19149 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.Beta1 > Reporter: Alexey Kazakov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.3.Beta1 > > > {code} > testGetDefaultInitialCase(org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest) Time elapsed: 0.002 sectestGetDefaultAndGetInstallationsAlternativeCase(org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest) Time elapsed: 0.008 sec <<< FAILURE! > java.lang.AssertionError: expected:<org.jboss.tools.forge.core.internal.runtime.ForgeEmbeddedRuntime@291bc55> but was:<null> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest.verifyEmbedded(ForgeRuntimesPreferencesTest.java:179) > at org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest.testGetDefaultAndGetInstallationsAlternativeCase(ForgeRuntimesPreferencesTest.java:163) > {code} > {code} > testForgeEmbeddedRuntime(org.jboss.tools.forge.core.process.ForgeEmbeddedRuntimeTest) Time elapsed: 0.001 sec <<< FAILURE! > org.junit.ComparisonFailure: expected:<1.[4.4].Final - embedded> but was:<1.[3.3].Final - embedded> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.jboss.tools.forge.core.process.ForgeEmbeddedRuntimeTest.testForgeEmbeddedRuntime(ForgeEmbeddedRuntimeTest.java:47) > {code} -- 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19376: ----------------------------------- Fix Version/s: 4.2.3.CR1 (was: 4.2.3.Beta1) Today is the 4.2.3.Beta1 code freeze. This issue is not something new for 4.2.3 so I'm moving it to CR1 hoping Rob will be able to figure out what is going on here and maybe provide a patch by the CR1 code freeze (March, 12). > 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.CR1, 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-3262) Deprecate Visual JSF Preview & Editing

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3262: -------------------------------------- As part of this deprecation we added a new dialog for Visual Editor - JBIDE-18177 (Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner) in Beta1. What else should be done for 8.1.0? We should document/announce the deprecation. Anything else? > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 8.1.0.GA > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19296) hibernate New and Noteworthy for 4.2.3.Beta1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19296?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19296. ---------------------------------- Resolution: Rejected I don't see any N&N for Beta1. [~koen.aers] please reopen the issue if I missed something. > hibernate New and Noteworthy for 4.2.3.Beta1 > -------------------------------------------- > > Key: JBIDE-19296 > URL: https://issues.jboss.org/browse/JBIDE-19296 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Alexey Kazakov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.3.Beta1 > > > 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 hibernate is not listed here check if there are issues that should be added and add them. > Document the ones relevant for hibernate by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19377) JBDS update site build sometimes fails with a dirty Jenkins workspace

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19377: ---------------------------------- Summary: JBDS update site build sometimes fails with a dirty Jenkins workspace Key: JBIDE-19377 URL: https://issues.jboss.org/browse/JBIDE-19377 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.3.0.Alpha1, 4.2.3.Beta1 Reporter: Nick Boldt {code} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (install) on project com.jboss.devstudio.core.site: An Ant BuildException has occured: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/sources/product/site/build.xml:113: /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/results/target not found. [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (install) on project com.jboss.devstudio.core.site: An Ant BuildException has occured: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/sources/product/site/build.xml:113: /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/results/target not found. {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Caused by this: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/build... So... working on a fix in 4.2.x and master now which defines a better default path. {code} <property name="output.dir" value="${basedir}"/> {code} Building locally to verify. -- 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