October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14960) BrowserSim/CordovaSim: externalize messages

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14960?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14960: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-vpe/pull/151, https://github.com/jbosstools/jbosstools-vpe/pull/179 (was: https://github.com/jbosstools/jbosstools-vpe/pull/151) > BrowserSim/CordovaSim: externalize messages > ------------------------------------------- > > Key: JBIDE-14960 > URL: https://issues.jboss.org/browse/JBIDE-14960 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Environment: All messages should be externalized > Reporter: Yahor Radtsevich > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Alpha1 > > > Messa -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15745) OpenShift Tools marker file changes are not committed on Publish

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15745?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15745. --------------------------------- Original issue JBIDE 15309 verified, this is close. As André said - in case of emergency open new one or reopen this. > OpenShift Tools marker file changes are not committed on Publish > ---------------------------------------------------------------- > > Key: JBIDE-15745 > URL: https://issues.jboss.org/browse/JBIDE-15745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final > Environment: Using Eclipse Kepler with JBoss OpenShift Tools 2.5.0.Final-v20130717-0249-B81 > Reporter: Katie Miller > Assignee: Andre Dietisheim > Labels: markers, openshift > Fix For: 4.1.1.Beta1 > > > When I add OpenShift marker files (those in .openshift/markers) with Eclipse, I have found the marker files are created but not added to the Git repository. This means when you then use the IDE to Publish, the marker files are not pushed to OpenShift Online. An easy one to try to test this is Hot Deploy; if the change were picked up, this would be reflected in the console messages when the app is rebuilt. > At the moment it looks like you have to do a manual 'git add .openshift/markers/*' before the files will be picked up, and also manually remove the files from Git when you want to delete a marker. I'm not sure if this is a bug or just a missing feature, but it does mean the user has to use the command line; it would be preferable to be able to stay in the IDE and have these file changes recognised by the IDE's Publish process. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15309) Marker wizard: the marker I add is not git added, committed and then pushed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15309?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15309. --------------------------------- Verified in JBDS 7.1.0.Beta1 Build id: Beta1-v20131026-0928-B470 > Marker wizard: the marker I add is not git added, committed and then pushed > --------------------------------------------------------------------------- > > Key: JBIDE-15309 > URL: https://issues.jboss.org/browse/JBIDE-15309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15825) JAX-RS problems don't show up after target runtime is set

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-15825: --------------------------------------- Summary: JAX-RS problems don't show up after target runtime is set Key: JBIDE-15825 URL: https://issues.jboss.org/browse/JBIDE-15825 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.1.1.Beta1 Reporter: Radoslav Rábara Fix For: 4.1.1.CR1 JAX-RS problems don't show up after target runtime is set on project that was created with target runtime set to <None>. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15789) Renaming HTML file doesn't change editor title

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15789?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-15789: ----------------------------------------- [~vpakan] Could you give more details on your Fedora installation (Arch, Desktop Manager, JDK/JRE version) and what JBT/JDBS version were tested on it? I'm using Fedora 19 x86_64 with Oracle JDK 1.6 and Oracle JDK 1.7 + JBT-4.1.1.Beta1a (Kepler SR1) on it and I'm not able to reproduce the issue - the file is always properly renamed, editor isn't closed and the title is properly changed in editor (actually the same editor is opened for a new file). But may be I'm able to emulate/set up something that pretty close to your configuration of Fedora? > Renaming HTML file doesn't change editor title > ---------------------------------------------- > > Key: JBIDE-15789 > URL: https://issues.jboss.org/browse/JBIDE-15789 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Linux KDE > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.2.x > > > 1. Create project with HTML file > 2. Open HTML file in VPE > 3. Rename HTML file in Package Explorer > ASSERT: File is renamed in Package Explorer > ERROR: Editor title of opened HTML file is not 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15789) Renaming HTML file doesn't change editor title

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15789?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-15789: ------------------------------------- I can't say if it's duplicate. On Fedora editor window stays open with no change in editor title as written in Jira description On Ubuntu editor window is closed. So two different scenarios when HTML file is renamed both are bugs > Renaming HTML file doesn't change editor title > ---------------------------------------------- > > Key: JBIDE-15789 > URL: https://issues.jboss.org/browse/JBIDE-15789 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Linux KDE > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.2.x > > > 1. Create project with HTML file > 2. Open HTML file in VPE > 3. Rename HTML file in Package Explorer > ASSERT: File is renamed in Package Explorer > ERROR: Editor title of opened HTML file is not 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15819) JSF XHTML Validator Ignores or Overrides Project-level XML Validation settings

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15819?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-15819: ------------------------------------------- Please note that this happens with a brand new workspace and gets somewhat muddled after that. > JSF XHTML Validator Ignores or Overrides Project-level XML Validation settings > ------------------------------------------------------------------------------ > > Key: JBIDE-15819 > URL: https://issues.jboss.org/browse/JBIDE-15819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.1.1.Alpha1 > Environment: Windows 7/JBDS 7.1 Beta 1 installed with SwitchYard Editor from the Kepler JBTIS (http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...) > Reporter: Brian Fitzpatrick > Assignee: Victor Rubezhny > Fix For: 4.2.0.Alpha1 > > > While testing the SwitchYard Editor, we have hit upon a strange error that occurs in a brand new workspace with JBDS 7.1 Beta 1 and the SwitchYard Editor installed. > To reproduce: > 1) Start with an empty workspace (with JBDS 7.1 Beta 1 and SwitchYard Editor installed) > 2) Create a new SwitchYard project. > 3) Add a new Bean component (drag the Bean implementation from the palette onto the composite (blue box) on the canvas). > 4) Save the project. > Though we by default turn off XML Validation on the new SwitchYard project, the XML validator is run and we find 3 or more errors off the bat. > We believe this is due to the JSF XHTML validator. If we turn it off (Window->Preferences->Validation; find XHTML Syntax Validator in the list and uncheck "Build" and "Manual"), the errors go away (as they should). And depending on what OS you're on (Linux seems to do one thing, Windows another), you can turn the XHTML Syntax Validator back on and either not see the errors or see the errors on a manual validation. > There are quite a few internal APIs used by the XHTML Validator, so we're not sure if that plays into it. Perhaps there's a static variable that doesn't get initialized properly until the validator is turned off and on during a workbench session. Or maybe this line should return null instead of the ValidationReport instance. : > https://github.com/jbosstools/jbosstools-javaee/blob/master/jsf/plugins/o... > We really don't know. But it shouldn't interfere with the XML Validation settings considering that none of the files in the project are XHTML files and none of them seem to match the rules for the validator. > The only workaround we've found is to turn off XML File validation at the workbench level (i.e. Window->Preferences->XML->XML Files->Validation; turn off "Honour all XML schema locations") instead of the project level. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2736) Split Web and Mobile Development into 2 categories in JBT & JBDS Central

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-2736. ------------------------------- This is done. Verified in JBDS 7.1.0.Beta1a B470. Closing. > Split Web and Mobile Development into 2 categories in JBT & JBDS Central > ------------------------------------------------------------------------ > > Key: JBDS-2736 > URL: https://issues.jboss.org/browse/JBDS-2736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Fix For: 7.1.0.Alpha2 > > > http://screencast.com/t/7vsajdz9o > Now that Cordova tools have been proposed, we need to split Web & Mobile into there own categories on the Software/Update tab. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2678) add EAP 6.1.1 to JBDS 7.1.0 installer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2678?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-2678. ------------------------------- I saw EAP 6.1.1 earlier in the Alpha builds and now I verified it again with JBDS 7.1.0.Beta1a B470. Closing. > add EAP 6.1.1 to JBDS 7.1.0 installer > ------------------------------------- > > Key: JBDS-2678 > URL: https://issues.jboss.org/browse/JBDS-2678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, requirements > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Alpha1, 7.1.0.Alpha2 > > > EAP 6.1.1 is supposed to be out in September, so we should update the installers to include the new version at that time. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15765) JPP 6.1 recognized as AS 7.2

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15765. ----------------------------------- Verified in JBDS 7.1.0 Beta1-v20131026-0928-B470 > JPP 6.1 recognized as AS 7.2 > ---------------------------- > > Key: JBIDE-15765 > URL: https://issues.jboss.org/browse/JBIDE-15765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: jpp 6.1 recognized as AS 72.jpg > > > JBoss Portal 6.1.0 Final is recognized as AS 7.2 in JBoss Runtime Detection (Type: AS, Version: 7.2). However, JPP 6.1.0 Beta is recognized correctly as JPP 6.1. -- 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, 5 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 October 2013