December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-8445) Do not create markers at internal attribute validation by XModel

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8445?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-8445: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Do not create markers at internal attribute validation by XModel > ---------------------------------------------------------------- > > Key: JBIDE-8445 > URL: https://issues.jboss.org/browse/JBIDE-8445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.2.0.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha2 > > > This framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. > It is ok to have some internal validation for model consistency, but it should not interfere with the standard framework. Markers should be created by delegates of the validation job. > Now, trees and forms of JBoss Tools editors recognize markers created by XModel and display them. We may try to replace this by > 1) either to be able to bind any markers with model objects > Profit: that would immensely improve displaying problems in tree/form in JBoss Tools editors > Possible Minus: It may be very resource consuming; > 2) or to store the found problems as internal objects, not as markers, and refactor editors/views to displaying them > Profit: Preserve feature at the current level > Minus: Developing internal framework that cannot be reused; > 3) or just drop it > Profit: No need for development, just do not create markers. > Minus: Problems in tree/form in JBoss Tools editors will not be displayed. Also, other possible unexpected aftermath should be addressed to. > -- 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-15258) Move performance tests in separate github repository from jbosstools-base/tests

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15258?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15258: ----------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Move performance tests in separate github repository from jbosstools-base/tests > ------------------------------------------------------------------------------- > > Key: JBIDE-15258 > URL: https://issues.jboss.org/browse/JBIDE-15258 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core, qa > Affects Versions: 4.1.0.CR1 > Reporter: Denis Golovin > Fix For: 4.2.0.Alpha2 > > -- 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-16228) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16228?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16228: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST] > -------------------------------------------------- > > Key: JBIDE-16228 > URL: https://issues.jboss.org/browse/JBIDE-16228 > 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.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1 [JST]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [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 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-16233) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Base]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16233?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16233: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Base] > --------------------------------------------------- > > Key: JBIDE-16233 > URL: https://issues.jboss.org/browse/JBIDE-16233 > 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.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1 [Base]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [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 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-16235) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16235?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16235: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE] > ----------------------------------------------------- > > Key: JBIDE-16235 > URL: https://issues.jboss.org/browse/JBIDE-16235 > 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.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1 [JavaEE]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [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 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-16226) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16226?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16226: ------------------------------------ Just a reminder, this can be closed when: * jobs are updated to point at 4.2.0.Alpha1x branch and are enabled * JBIDE-16226: jbosstools-build/parent is built from new 4.2.0.Alpha1x branch (_42 job) * JBIDE-16230: jbosstools-build-sites/aggregate/* are built from new 4.2.0.Alpha1x branch (_42 job) [3 jobs] * JBIDE-16244: jbosstools-discovery is built from new 4.2.0.Alpha1 branch (_42 job) * JBDS-2855: jbdevstudio-product is built from new 4.2.0.Alpha1 branch (_80 job) > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch > -------------------------------------------- > > Key: JBIDE-16226 > URL: https://issues.jboss.org/browse/JBIDE-16226 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-2855 -- 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-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-16161: --------------------------------------- Any movement on this issue yet? Builds are stuck now, because of one missing bundle. > Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Mickael Istria > Priority: Critical > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- 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-16119) CordovaSim: Need to make panels design more user-friendly

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16119?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-16119: ------------------------------------- Excellent, I seem to have a need to click on icons :-) > CordovaSim: Need to make panels design more user-friendly > --------------------------------------------------------- > > Key: JBIDE-16119 > URL: https://issues.jboss.org/browse/JBIDE-16119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Environment: Mac OSX lion > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha2 > > Attachments: collapsible_set.png, CordovaSim.jpg, listview.png > > > See video, trying to get access to the accelerometer drop-down > http://www.screencast.com/t/RBwdqXxeCsHJ -- 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-16252) Deployed module on OpenShift (server adapter) should be associated with '/'

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16252?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-16252: ---------------------------------- Description: The deployed project on OpenShift is a module of the OpenShift Application Server Adapter. When selecting this module and doing 'Show In>Web browser', the URL given to the browser ends with a '/app' context which is wrong, it should be '/'. Otherwise, the user (or speaker in front of an audience ;-) ) will have a 404 error :-/ Furthermore, when the user is used to select the module under a classic JBossAS 7 server adapter, he gets confused if he needs to select the server for the OpenShift deployed application. was: The deployed project on OpenShift is a module of the OpenShift Application Server Adapter. When selecting this module and doing 'Show In>Web browser', the URL given to the browser ends with a '/app' context which is wrong, it should be '/'. Otherwise, the user (or speaker in front of an audience ;-) ) will have a 404 error :-/ > Deployed module on OpenShift (server adapter) should be associated with '/' > --------------------------------------------------------------------------- > > Key: JBIDE-16252 > URL: https://issues.jboss.org/browse/JBIDE-16252 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > > The deployed project on OpenShift is a module of the OpenShift Application Server Adapter. > When selecting this module and doing 'Show In>Web browser', the URL given to the browser ends with a '/app' context which is wrong, it should be '/'. > Otherwise, the user (or speaker in front of an audience ;-) ) will have a 404 error :-/ > Furthermore, when the user is used to select the module under a classic JBossAS 7 server adapter, he gets confused if he needs to select the server for the OpenShift deployed application. -- 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-16252) Deployed module on OpenShift (server adapter) should be associated with '/'

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-16252: ------------------------------------- Summary: Deployed module on OpenShift (server adapter) should be associated with '/' Key: JBIDE-16252 URL: https://issues.jboss.org/browse/JBIDE-16252 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.1.Final Reporter: Xavier Coulon The deployed project on OpenShift is a module of the OpenShift Application Server Adapter. When selecting this module and doing 'Show In>Web browser', the URL given to the browser ends with a '/app' context which is wrong, it should be '/'. Otherwise, the user (or speaker in front of an audience ;-) ) will have a 404 error :-/ -- 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