April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16968) Performance issue when importing windup project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16968?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16968: --------------------------------------------- Thanks [~jsightler] the jstack shows you have installed Fuse camel tooling and it indicates it is the one doing something "slow" but can't be fully sure. Can you tell me what versions you have installed exactly and what projects/files you where importing/using and if you were doing any Camel file editing ? > Performance issue when importing windup project > ----------------------------------------------- > > Key: JBIDE-16968 > URL: https://issues.jboss.org/browse/JBIDE-16968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Jess Sightler > Attachments: jstack1.txt > > > User interface freezes and Gnome pops up the "JBoss - JBoss Developer Studio" is not responding dialog. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16968) Performance issue when importing windup project

by Jess Sightler (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16968?page=com.atlassian.jira.plugi... ] Jess Sightler updated JBIDE-16968: ---------------------------------- Attachment: jstack1.txt jstack during the freeze > Performance issue when importing windup project > ----------------------------------------------- > > Key: JBIDE-16968 > URL: https://issues.jboss.org/browse/JBIDE-16968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Jess Sightler > Attachments: jstack1.txt > > > User interface freezes and Gnome pops up the "JBoss - JBoss Developer Studio" is not responding dialog. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16968) Performance issue when importing windup project

by Jess Sightler (JIRA)

Jess Sightler created JBIDE-16968: ------------------------------------- Summary: Performance issue when importing windup project Key: JBIDE-16968 URL: https://issues.jboss.org/browse/JBIDE-16968 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Jess Sightler User interface freezes and Gnome pops up the "JBoss - JBoss Developer Studio" is not responding dialog. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16968) Performance issue when importing windup project

by Jess Sightler (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16968?page=com.atlassian.jira.plugi... ] Jess Sightler commented on JBIDE-16968: --------------------------------------- Project is here: https://github.com/windup/windup > Performance issue when importing windup project > ----------------------------------------------- > > Key: JBIDE-16968 > URL: https://issues.jboss.org/browse/JBIDE-16968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Jess Sightler > > User interface freezes and Gnome pops up the "JBoss - JBoss Developer Studio" is not responding dialog. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16358) "jboss-client_6_0.xsd" is missing in XML catalog

by Wolfgang Knauf (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16358?page=com.atlassian.jira.plugi... ] Wolfgang Knauf commented on JBIDE-16358: ---------------------------------------- For the use case "create XML file based on schema file from XML catalog", the version with {code:xml} <uri name="http://www.jboss.com/xml/ns/javaee" ... {code} results in a xml file which cannot be validated because of a wrong schema location (see above). Here the version with the "real" web url creates a correct file. I am not sure whether version 1 is helpful in any case. All "jboss-client_x_y.xsd" files have the same namespace URI (and also "jboss_x_y.xsd"), so if a xml file just declares the default namespace without schema location hint, it would not be possible to pick the correct file to validate against: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <jboss-client xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> ... {code} By the way: taking a look at my %WILDFLY_HOME%\docs\schema" directory, there are a lot more "jboss-...xsd" files (not the "jboss-as....xsd" files, which are needed only for server config), which all are not part of the catalog. > "jboss-client_6_0.xsd" is missing in XML catalog > ------------------------------------------------ > > Key: JBIDE-16358 > URL: https://issues.jboss.org/browse/JBIDE-16358 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.1.1.Final > Reporter: Wolfgang Knauf > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.0.Beta2 > > Attachments: jboss_client_catalog.png, jboss_client_wizard.png > > > See subject -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16950?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16950: ------------------------------------- So, I've finally found out the cause of the issue : we add a deployment scanner on server startup, which competes with the one from WF/AS. >From JBT, deploying an app can seem to be OK (no errors in log, app accessible from browser) but you'll see a foo.war.failed file instead of foo.war.deployed in the deployments folder. The error message talks about duplicate resource. If the server is started from JBT and you manually create a foo.war folder with a foo.war.dodeploy file under the deployments directory, deployment will fail as well, with the same message. Now if, in the WF/AS properties page, you uncheck "Add missing deployment scanners..." in the Deployment Scanners section, then deployment from JBT will succeed. The problem only occurs on windows. > Very frequently, webapps are being undeployed right after being deployed > ------------------------------------------------------------------------ > > Key: JBIDE-16950 > URL: https://issues.jboss.org/browse/JBIDE-16950 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta1 > > > I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed. > See http://screencast.com/t/JmwA0TlBrDWX > The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs : > {noformat} > 14:13:45,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war") > 14:13:45,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme > 14:13:45,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war") > 14:13:50,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme > 14:13:50,730 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms > 14:13:50,999 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war") > 14:13:56,004 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy > {noformat} > Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast) -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16822) Dark text on dark background in Central

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16822?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16822: --------------------------------------- [~rhopp] The PR fixes the issue you have described. It isn't included into JBT 4.2.0.Beta1a. > Dark text on dark background in Central > --------------------------------------- > > Key: JBIDE-16822 > URL: https://issues.jboss.org/browse/JBIDE-16822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.2.CR1, 4.2.0.Alpha2 > Environment: Fedora 20, KDE 4.12.3, Oxygen color theme > Reporter: Radim Hopp > Assignee: Snjezana Peco > Labels: respin-a > Fix For: 4.2.0.Beta1 > > Attachments: central-popup.png, centralHoverColors.png > > > There is dark text on dark background in hover popup of project examples. > See screenshot: > !central-popup.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16946) JBoss buzz: File not found: http://planet.jboss.org/feeds/buzz

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16946?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-16946. --------------------------------- Resolution: Done http://planet.jboss.org/feeds/buzz is up again > JBoss buzz: File not found: http://planet.jboss.org/feeds/buzz > -------------------------------------------------------------- > > Key: JBIDE-16946 > URL: https://issues.jboss.org/browse/JBIDE-16946 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: jboss-buzz.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16957) no difference between beta1 and beta1a updatesites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16957?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16957: --------------------------------------------- pushing to beta1a url which is inside staging is fine. it was bad upload. > no difference between beta1 and beta1a updatesites > -------------------------------------------------- > > Key: JBIDE-16957 > URL: https://issues.jboss.org/browse/JBIDE-16957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Beta1 > > > something is funky here. > eclipse doesn't give me any updates for this new beta1a site. > Thus I tried running p2diff and browse via p2browser. The binary content except the category are identical. > See difference at https://gist.github.com/maxandersen/352153881b657fbe2ecb > none of the plugins like open shift or server has changed. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16967) Failure to replace Variables on Config xml files for Cordova plug-ins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16967?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16967: --------------------------------------------- +1 for that trivial but crucial for push fix ;) > Failure to replace Variables on Config xml files for Cordova plug-ins > --------------------------------------------------------------------- > > Key: JBIDE-16967 > URL: https://issues.jboss.org/browse/JBIDE-16967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > HMT fails to replace the variable values on config.xml fails when installing cordova plugins. For example if a variable such as $PACKAGE_NAME needs to be replaced on AndroidManifest.xml it is skipped and not replaced. On android this causes apk not installed error on most occasions. -- 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

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 April 2014