December 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-177) Cannot save process definition which contains a local variable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-177?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-177: ----------------------------------------------- Andrej Podhradsky <apodhrad(a)redhat.com> changed the Status of [bug 1008573|https://bugzilla.redhat.com/show_bug.cgi?id=1008573] from ON_QA to VERIFIED > Cannot save process definition which contains a local variable > -------------------------------------------------------------- > > Key: JBTIS-177 > URL: https://issues.jboss.org/browse/JBTIS-177 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPMN2 > Reporter: Len DiMaggio > Assignee: Paul Leacu > Fix For: 4.1.3 > > > Eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=417203 Will be resolved in JBTIS 4.1.3.beta2 and JBDSIS 7.0.0.beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15888: -------------------------------- Attachment: springmvc-test.xml > Update the Spring Archetype reference > ------------------------------------- > > Key: JBIDE-15888 > URL: https://issues.jboss.org/browse/JBIDE-15888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Joshua Wilson > Assignee: Fred Bricon > Labels: spring > Fix For: 4.1.1.Final > > Attachments: springmvc-test.xml > > > I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16301) No combo to select Target Runtime in examples dilaog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16301?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16301: -------------------------------- Fix Version/s: 4.2.x > No combo to select Target Runtime in examples dilaog > ---------------------------------------------------- > > Key: JBIDE-16301 > URL: https://issues.jboss.org/browse/JBIDE-16301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.Final > Reporter: Denis Golovin > Fix For: 4.2.x > > Attachments: Selection_025.png > > > Target Runtime combo is not visible in Examples dialog > !Selection_025.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2871) Maven Pop-up should enable/expose mvn clean package

by Jim Tyrrell (JIRA)

[ https://issues.jboss.org/browse/JBDS-2871?page=com.atlassian.jira.plugin.... ] Jim Tyrrell updated JBDS-2871: ------------------------------ Attachment: Screen shot 2013-12-13 at 6.16.55 AM.png > Maven Pop-up should enable/expose mvn clean package > --------------------------------------------------- > > Key: JBDS-2871 > URL: https://issues.jboss.org/browse/JBDS-2871 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jim Tyrrell > Attachments: Screen shot 2013-12-13 at 6.16.55 AM.png > > > When building and importing projects, every so often something goes sideways in the import/building of a project. I have to jump to the mvn command line and often I need to run mvn clean package to execute a "build" that re-sets whatever went sideways. Generally if the network goes away the above command will enable it to work. > If you know of other commands that should be exposed please let me know. > I wonder if Update Project should execute this command? I don't know enough about maven to know if this makes sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2871) Maven Pop-up should enable/expose mvn clean package

by Jim Tyrrell (JIRA)

Jim Tyrrell created JBDS-2871: --------------------------------- Summary: Maven Pop-up should enable/expose mvn clean package Key: JBDS-2871 URL: https://issues.jboss.org/browse/JBDS-2871 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jim Tyrrell Attachments: Screen shot 2013-12-13 at 6.16.55 AM.png When building and importing projects, every so often something goes sideways in the import/building of a project. I have to jump to the mvn command line and often I need to run mvn clean package to execute a "build" that re-sets whatever went sideways. Generally if the network goes away the above command will enable it to work. If you know of other commands that should be exposed please let me know. I wonder if Update Project should execute this command? I don't know enough about maven to know if this makes sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16214) Code Coverage jobs needs to have locally available measured plugins

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-16214: ------------------------------------- I'm running it on Jenkins using 3 maven builds: 1. First build JBT component e.g. JSF 2. Build org.jboss.tools.ui.bot.ext 3. Build and run tests from org.jboss.tools.jsf.ui.bot,tests Post build actions are collecting test results and code coverage from step 3 and applies it to source and binaries from step 1 > Code Coverage jobs needs to have locally available measured plugins > ------------------------------------------------------------------- > > Key: JBIDE-16214 > URL: https://issues.jboss.org/browse/JBIDE-16214 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.CR1 > Reporter: Vlado Pakan > Assignee: Mickael Istria > Fix For: 4.1.x > > > Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site. > When these are built locally prior to build calculating code coverage it returns correct results. > Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build. > We need to find way how to fix this. > It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Romaine Herrera (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Romaine Herrera edited comment on JBIDE-2720 at 12/13/13 7:49 AM: ------------------------------------------------------------------ [~carsten.pfeiffer] Can you walk me through on how to deal with that bug? because I dont know how to fix it and can you send me the steps by steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com was (Author: dagz213): [~carsten.pfeiffer] Can you walk me thought on how to deal with that bug? because I dont know how to fix it and can you send me the steps by steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Romaine Herrera (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Romaine Herrera edited comment on JBIDE-2720 at 12/13/13 7:49 AM: ------------------------------------------------------------------ [~carsten.pfeiffer] Can you walk me through on how to deal with that bug? because I dont know how to fix it and can you send me the steps by steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com, Thank you. was (Author: dagz213): [~carsten.pfeiffer] Can you walk me through on how to deal with that bug? because I dont know how to fix it and can you send me the steps by steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Romaine Herrera (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Romaine Herrera commented on JBIDE-2720: ---------------------------------------- [~carsten.pfeiffer] Can you walk me thought on how to deal with that bug? because I dont know how to fix it and can you send me the steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Romaine Herrera (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Romaine Herrera edited comment on JBIDE-2720 at 12/13/13 7:39 AM: ------------------------------------------------------------------ [~carsten.pfeiffer] Can you walk me thought on how to deal with that bug? because I dont know how to fix it and can you send me the steps by steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com was (Author: dagz213): [~carsten.pfeiffer] Can you walk me thought on how to deal with that bug? because I dont know how to fix it and can you send me the steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2013