July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20210) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20210?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20210: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices] > --------------------------------------------------------------------------------------- > > Key: JBIDE-20210 > URL: https://issues.jboss.org/browse/JBIDE-20210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Webservices]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20131) Upgrade Forge Runtime to 2.17.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20131?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-20131. ------------------------------------- Labels: new_and_noteworthy (was: ) Resolution: Done > Upgrade Forge Runtime to 2.17.0.Final > ------------------------------------- > > Key: JBIDE-20131 > URL: https://issues.jboss.org/browse/JBIDE-20131 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > As Final is not yet released, upgrade to 2.17.0.Alpha2 instead -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20187. --------------------------------- Resolution: Done The errai archetype is no longer built as part of the offline script, making the error no longer show up. > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Misha Ali > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.0.Beta2 > > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20187: -------------------------------- Priority: Minor (was: Major) > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Misha Ali > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.0.Beta2 > > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20279) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20279?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20279: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [JST] > ------------------------------------------------- > > Key: JBIDE-20279 > URL: https://issues.jboss.org/browse/JBIDE-20279 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [JST]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20278) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20278?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20278: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [JavaEE] > ---------------------------------------------------- > > Key: JBIDE-20278 > URL: https://issues.jboss.org/browse/JBIDE-20278 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [JavaEE]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20012) Jboss Tools HTML editor not validating syntax using html5 doctype (xhtml doctype is OK)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20012?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20012: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Jboss Tools HTML editor not validating syntax using html5 doctype (xhtml doctype is OK) > --------------------------------------------------------------------------------------- > > Key: JBIDE-20012 > URL: https://issues.jboss.org/browse/JBIDE-20012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Environment: windows 7, java 8, eclipse ide for java ee developers (luna sr2 and jboss tools 4.2.3.Final) (mars rc3 and 4.3.0.Alpha2) > Reporter: Euclides Melo > Assignee: Victor Rubezhny > Fix For: 4.3.0.CR1 > > Attachments: html5_doctype.jpg, xhtml_doctype.jpg > > > Editing two xhtml files in a fresh eclipse, fresh workspace, fresh default dynamic web project (with jsf capabilities): > In one file, there is the xhtml doctype. In the other file, the html5 doctype. > The issue: > Validation (syntax) only occurs in the file with the xhtml doctype. > (attached two screens showing the error) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20275) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Base]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20275?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20275: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Base] > -------------------------------------------------- > > Key: JBIDE-20275 > URL: https://issues.jboss.org/browse/JBIDE-20275 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Base]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19423) Multiple syntax errors with latest imported ionic project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19423?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19423: ----------------------------------- Component/s: javascript (was: jsp/jsf/xml/html source editing) > Multiple syntax errors with latest imported ionic project > --------------------------------------------------------- > > Key: JBIDE-19423 > URL: https://issues.jboss.org/browse/JBIDE-19423 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.2.3.Beta1 > Environment: JBDS 8.1.0.Beta1 > Reporter: Jiri Peterka > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: scr.png > > > I see multiple compilation problems after importing current ionic project based on this workflow: > https://www.youtube.com/watch?v=UFuMuEqonkQ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20063: -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 2015