December 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-11882) Errors running builder 'JavaScript Validator'

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11882?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-11882 at 12/24/12 5:05 AM: ------------------------------------------------------------------- Known BugZilla issues For JBIDE-11652 (Coping here due to track UpStream issues because JBIDE-11652 is marked as resolved): - https://bugs.eclipse.org/bugs/show_bug.cgi?id=376809 (RESOLVED FIXED, 3.4.1). The patch is proposed for JSDT issue in BugZilla. Patch is applied, targeted milestone is 3.4.1. - https://bugs.eclipse.org/bugs/show_bug.cgi?id=356446 as well as https://bugs.eclipse.org/bugs/show_bug.cgi?id=350693 (Both issues are new, Not targeted yet, duplicates). The patch is proposed for JSDT issue [356446|https://bugs.eclipse.org/bugs/show_bug.cgi?id=356446] in BugZilla and covers both issues. - https://bugs.eclipse.org/bugs/show_bug.cgi?id=344745 (New, Not targeted yet). The patch is proposed for JSDT issue in BugZilla. - https://bugs.eclipse.org/bugs/show_bug.cgi?id=357353 (New, Not targeted yet). The patch is proposed for JSDT issue in BugZilla. - https://bugs.eclipse.org/bugs/show_bug.cgi?id=349020 (New, Not targeted yet). There is a proposal to use fixed grammar for the parser. was (Author: vrubezhny): Known BugZilla issues For JBIDE-11652 (Coping here due to track UpStream issues because JBIDE-11652 is marked as resolved): - https://bugs.eclipse.org/bugs/show_bug.cgi?id=376809 (RESOLVED FIXED, 3.4.1). The patch is proposed for JSDT issue in BugZilla. Patch is applied, targeted milestone is 3.4.1. - https://bugs.eclipse.org/bugs/show_bug.cgi?id=356446 as well as https://bugs.eclipse.org/bugs/show_bug.cgi?id=350693 (Both issues are new, Not targeted yet, duplicates). The patch is proposed for JSDT issue [356446|https://bugs.eclipse.org/bugs/show_bug.cgi?id=356446] in BugZilla and covers both issues. - https://bugs.eclipse.org/bugs/show_bug.cgi?id=344745 (New, Not targeted yet). The patch is proposed for JSDT issue in BugZilla. - https://bugs.eclipse.org/bugs/show_bug.cgi?id=357353 (New, Not targeted yet). The patch is proposed for JSDT issue in BugZilla. > Errors running builder 'JavaScript Validator' > --------------------------------------------- > > Key: JBIDE-11882 > URL: https://issues.jboss.org/browse/JBIDE-11882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 3.3.0.Beta3 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Priority: Minor > Labels: jsdt > Fix For: LATER > > > Errors running builder 'JavaScript Validator' occurs when importing some example projects with JavaScripts. > See: > - JBIDE-11652: Errors running builder 'JavaScript Validator' on project 'ticket-monster' (Resolved with a workaround that disables validation of JavaScripts) > - JBIDE-11630: javascript validation error occurs when creating birt project > The UpStream issue is created as an overall issue for JSDT problems. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13333) Fixing Eclipse/Kepler

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13333?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-13333: ----------------------------------------- JSDT related issues listed in JBIDE-11882 > Fixing Eclipse/Kepler > --------------------- > > Key: JBIDE-13333 > URL: https://issues.jboss.org/browse/JBIDE-13333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: UpStream > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > "container" issue for issues related to fixes important to get into Kepler. > Please link your Eclipse/Kepler issue to this one instead of using subtasks. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13337) M2E not setting "Run Java Application" classpath properly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13337?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13337: -------------------------------- Component/s: UpStream > M2E not setting "Run Java Application" classpath properly > --------------------------------------------------------- > > Key: JBIDE-13337 > URL: https://issues.jboss.org/browse/JBIDE-13337 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Environment: JBDS 6.0 > Reporter: Pete Muir > Assignee: Fred Bricon > > Take a look at this screencast - http://screencast.com/t/bOg9G8XqT - the dependent project is not appearing properly in the dependencies when you run the main class. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13337) M2E not setting "Run Java Application" classpath properly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13337?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13337: ------------------------------------- This is a known, long standing bug in m2e/m2e-wtp. Basically, m2e doesn't support workspace project "classifier" dependencies : https://bugs.eclipse.org/bugs/show_bug.cgi?id=368230#c9 > M2E not setting "Run Java Application" classpath properly > --------------------------------------------------------- > > Key: JBIDE-13337 > URL: https://issues.jboss.org/browse/JBIDE-13337 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Environment: JBDS 6.0 > Reporter: Pete Muir > Assignee: Fred Bricon > > Take a look at this screencast - http://screencast.com/t/bOg9G8XqT - the dependent project is not appearing properly in the dependencies when you run the main class. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12974: ------------------------------- Assignee: Martin Malina (was: Nick Boldt) > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.x > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12974: ------------------------------------ I've disabled building and running the soa-related tests (those contained in the soa profile). Having done so, I can successfully build ... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... --> http://download.jboss.org/jbosstools/builds/staging/jbosstools-integratio... but there are test failures as noted above: {code} [INFO] org.jboss.ide.eclipse.as.ui.bot.test .............. FAILURE [11:58.005s] [INFO] org.jboss.tools.runtime.as.ui.bot.test ............ FAILURE [4:50.663s] {code} Still, it's a start, right? :D > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12974: ------------------------------------ Building running here [0] from my fork [1] (uses this PR [2]). [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... [1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2 [2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94 To run locally, you need these settings: {code} mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} ./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt ./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt ./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt {code} > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12974 at 12/23/12 4:31 PM: -------------------------------------------------------------- Building running here [0] from my fork [1] (uses this PR [2]). [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... [1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2 [2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94 To run locally, you need these settings: {code} mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} ./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE! ./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE! ./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE! {code} was (Author: nickboldt): Building running here [0] from my fork [1] (uses this PR [2]). [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... [1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2 [2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94 To run locally, you need these settings: {code} mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} ./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt ./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt ./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt {code} > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12974 at 12/23/12 4:31 PM: -------------------------------------------------------------- Building running here [0] from my fork [1] (uses this PR [2]). [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... [1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2 [2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94 To run locally, you need these settings: {code} mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} Still having some problems w/ test failures in a couple test plugins, which is why I'm running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} ./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE! ./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE! ./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE! {code} was (Author: nickboldt): Building running here [0] from my fork [1] (uses this PR [2]). [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... [1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2 [2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94 To run locally, you need these settings: {code} mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} ./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE! ./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE! ./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE! {code} > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13337) M2E not setting "Run Java Application" classpath properly

by Pete Muir (JIRA)

Pete Muir created JBIDE-13337: --------------------------------- Summary: M2E not setting "Run Java Application" classpath properly Key: JBIDE-13337 URL: https://issues.jboss.org/browse/JBIDE-13337 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Environment: JBDS 6.0 Reporter: Pete Muir Assignee: Fred Bricon Take a look at this screencast - http://screencast.com/t/bOg9G8XqT - the dependent project is not appearing properly in the dependencies when you run the main class. -- 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

11 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2012