September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2731) Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2731?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2731: ----------------------------- CDW devel_ack: ? (was: +) CDW pm_ack: + (was: ?) > Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any) > --------------------------------------------------------------------------------------------- > > Key: JBDS-2731 > URL: https://issues.jboss.org/browse/JBDS-2731 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: visualeditor > Reporter: Max Rydahl Andersen > > We can't fix eclipse validation markers of ng-app in Kepler but we can at least make it easier to write them by adding content assist for them as done for jquery data. > It won't include dynamic content though - that will have to wait for next major release. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2731) Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2731?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-2731: --------------------------------- CDW devel_ack: + (was: ?) Status: New (was: New) > Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any) > --------------------------------------------------------------------------------------------- > > Key: JBDS-2731 > URL: https://issues.jboss.org/browse/JBDS-2731 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: visualeditor > Reporter: Max Rydahl Andersen > > We can't fix eclipse validation markers of ng-app in Kepler but we can at least make it easier to write them by adding content assist for them as done for jquery data. > It won't include dynamic content though - that will have to wait for next major release. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15401) CLONE - jbosstools-server API Compatibility for master

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15401?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15401. --------------------------------- Assignee: Rob Stryker Resolution: Done In general this is fixed in master, but it's not 100% for me. The only remaining errors is that apitools is angry that I set 2.4 as the introduction for some new APIs which exist in maintenance currently. The api's were added for astools 2.4.101 in maintenance, and, since apitools is comparing master to baseline (jbds7.0.0.GA) it doesn't like it. My only options here are to either change the since tags to 2.5 (which would be innaccurate) or to ignore the few errors that it doesn't like. So, for now, I choose to ignore those few. Most of the other complaints were about things like my Messages class being in a public package, so additions to it count as new API, etc etc. Several small things like this, but absolutely no critical api breakages. > CLONE - jbosstools-server API Compatibility for master > ------------------------------------------------------- > > Key: JBIDE-15401 > URL: https://issues.jboss.org/browse/JBIDE-15401 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Labels: api-compatibility > Fix For: 4.2.0.Alpha1 > > > Verify Latest version from jbosstools-server/master branch has no API Compatibility 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4160) Add option in JBoss ESB Editor to disable an ESB action

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4160?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBIDE-4160: ------------------------------ Assignee: Brian Fitzpatrick > Add option in JBoss ESB Editor to disable an ESB action > ------------------------------------------------------- > > Key: JBIDE-4160 > URL: https://issues.jboss.org/browse/JBIDE-4160 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: esb > Affects Versions: 3.0.0.GA > Environment: JBDS 2.0.0.GA > Reporter: Joao Viragine > Assignee: Brian Fitzpatrick > Priority: Optional > Fix For: LATER > > > It would be great if we could disable an specific action in ESB. > E.g. > <action class="org.jboss.soa.esb.actions.SystemPrintln" name="Println" enabled="false"> > <property name="message" value="JBoss ESB Rulez"/> > </action> -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-14818: ----------------------------------- Assignee: Andre Dietisheim (was: Rob Stryker) Passing to you, andre. > there's no "deployments" page for OpenShift that would allow me to rename a module > ---------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.0.Alpha1 > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15398: ----------------------------------- Fix Version/s: 4.2.x > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Fix For: 4.2.x > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15398: ----------------------------------- Assignee: Viacheslav Kabanovich > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15398: ----------------------------------- Priority: Critical (was: Major) > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.x > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15430) Chrome regression because of invalid content-lenght returned with special characters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15430?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15430: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Please review the PR. > Chrome regression because of invalid content-lenght returned with special characters > ------------------------------------------------------------------------------------- > > Key: JBIDE-15430 > URL: https://issues.jboss.org/browse/JBIDE-15430 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Alpha1 > > > When the HTML entity in the HTTP response contains special characters and the livereload script is injected in that entity, the computed content-lenght header is invalid, which causes Chrome to not render the returned HTML page *at all*. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15293) BrowserSim/CordovaSim: add logging callbacks to Eclipse

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15293?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-15293: ------------------------------------------ Aggregate PR#156 contains fixes for 4.1.1.Alpha1. > BrowserSim/CordovaSim: add logging callbacks to Eclipse > ------------------------------------------------------- > > Key: JBIDE-15293 > URL: https://issues.jboss.org/browse/JBIDE-15293 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > Attachments: screenshot.png > > > If something went wrong in BrowserSim/CordovaSim then an error is printed to the console. It would be much better if the error was shown in the Eclipse error log. -- 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, 7 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 September 2013