December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15902) Regarding JSON to JSON Transfermation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15902?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-15902. --------------------------------------- Resolution: Incomplete Description please use forums for user questions. > Regarding JSON to JSON Transfermation > ------------------------------------- > > Key: JBIDE-15902 > URL: https://issues.jboss.org/browse/JBIDE-15902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: siva maturi > > Hi, > How to do JSON to JSON convertion using Smooks -- 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-16245) Show correct version of integration tests repo web page

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16245?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16245: --------------------------------------- First step is to change the site version to something more meaningful. > Show correct version of integration tests repo web page > ------------------------------------------------------- > > Key: JBIDE-16245 > URL: https://issues.jboss.org/browse/JBIDE-16245 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.1.1.CR1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.2.Final > > > The integration tests repo is here: > http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/ > At the top it says: > Latest Build: 1.0.0.CR1 > We should display something more meaningful. > If you take core tests for example: > http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > They say: > Latest Build: 4.2.0-SNAPSHOT (Alpha1-v20131205-0707-B2751) -- 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-16245) Show correct version of integration tests repo web page

by Martin Malina (JIRA)

Martin Malina created JBIDE-16245: ------------------------------------- Summary: Show correct version of integration tests repo web page Key: JBIDE-16245 URL: https://issues.jboss.org/browse/JBIDE-16245 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.1.1.CR1 Reporter: Martin Malina Assignee: Martin Malina Fix For: 4.1.2.Final The integration tests repo is here: http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/ At the top it says: Latest Build: 1.0.0.CR1 We should display something more meaningful. If you take core tests for example: http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ They say: Latest Build: 4.2.0-SNAPSHOT (Alpha1-v20131205-0707-B2751) -- 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] (JBDS-2852) Database/source/connection Usability

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2852: -------------------------------------- Component/s: integration > Database/source/connection Usability > ------------------------------------ > > Key: JBDS-2852 > URL: https://issues.jboss.org/browse/JBDS-2852 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: integration > Reporter: Burr Sutter > > Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge. > Forge is involved as it can generate entities from schema > Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy > Persistence.xml may needed to be tweaked for the datasource > End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed. > What happens when a project that needs a database connection is imported into the IDE? > This was partially addressed with > https://issues.jboss.org/browse/JBIDE-15263 > Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow. -- 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-16177) Configure Maven Repositories Dialog Cancel

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16177?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16177: ---------------------------------------- Component/s: maven > Configure Maven Repositories Dialog Cancel > ------------------------------------------ > > Key: JBIDE-16177 > URL: https://issues.jboss.org/browse/JBIDE-16177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > > Hitting the Cancel button produces the following error: > An error has occurred. See error log for more details. > Argument cannot be null > http://screencast.com/t/8cNrfyB9A > Steps to Reproduce: > 1) While JDBS is running, edit your settings.xml to remove maven.repository.redhat.com - just remove it from <activeProfiles> > 2) Back in JBDS, hit HTML5 Project on JBoss Central > 3) Select EAP 6.1 in the Target Runtime > 4) Click on the word "repository" in the warning near the bottom of the dialog > 5) Click Cancel > and in some cases, I notice the error message might pop-up even before I can visit the subsequent 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16177) Configure Maven Repositories Dialog Cancel

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16177?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16177: --------------------------------------------- [~burrsutter] would help if you attached what is in the error log for this error. Would give the full stacktrace. > Configure Maven Repositories Dialog Cancel > ------------------------------------------ > > Key: JBIDE-16177 > URL: https://issues.jboss.org/browse/JBIDE-16177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > > Hitting the Cancel button produces the following error: > An error has occurred. See error log for more details. > Argument cannot be null > http://screencast.com/t/8cNrfyB9A > Steps to Reproduce: > 1) While JDBS is running, edit your settings.xml to remove maven.repository.redhat.com - just remove it from <activeProfiles> > 2) Back in JBDS, hit HTML5 Project on JBoss Central > 3) Select EAP 6.1 in the Target Runtime > 4) Click on the word "repository" in the warning near the bottom of the dialog > 5) Click Cancel > and in some cases, I notice the error message might pop-up even before I can visit the subsequent 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2843) AngularJS Usability

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2843: ------------------------------------------- Phase 1 already done in Luna - users need to go and say they are ok with non-valid html5. Ctrl+1 on the warning for ng-* would fix that. similar done in netbeans and intellij afaik. Phase 2 - needs separate jira. But no matter what it will still show errors for ng-* until users accepts invalid html. Phase 3 - code assist for what exactly ? you mean angular expressions {{ }} ? (requires javascript engine. Have prototype for it using your local browser but its not exactly easy for user to setup) Phase 4: This is hard, but probably easier for user than Phase 3 - but it requires massive work. Phase 5: Widget palette for what ? angular widgets don't exist yet afaik. Know of any other work going on making that happen ? > AngularJS Usability > ------------------- > > Key: JBDS-2843 > URL: https://issues.jboss.org/browse/JBDS-2843 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > > Related to JBIDE-14597 > Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML > Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code > Phase 3) Code Assist (cntrl-space) in .html > Phase 4) Code Assist (cntrl-space) in .js > Phase 5) Widget Palette (like our jQuery Mobile palete) -- 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] (JBDS-2848) Anonymous Usage Stats

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2848: -------------------------------------- Component/s: usage > Anonymous Usage Stats > --------------------- > > Key: JBDS-2848 > URL: https://issues.jboss.org/browse/JBDS-2848 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: usage > Reporter: Burr Sutter > Assignee: Andre Dietisheim > > We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage". > Areas worth tracking include (in priority order): > - Use of the OpenShift Wizard to successful completion vs error > - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8) > - Successful installation of the features found on Software/Update tab of JBoss Central > - Use of the JSF/RichFaces Visual Page Editor > - Use of the Hibernate Tooling > - Use of the jQuery Mobile Palette > - Use of BrowserSim > - Use of CordovaSim > We will also need to update http://www.jboss.org/tools/usage > Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool) > Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future. -- 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] (JBDS-2848) Usage Stats for actual used features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2848: -------------------------------------- Summary: Usage Stats for actual used features (was: Anonymous Usage Stats) > Usage Stats for actual used features > ------------------------------------ > > Key: JBDS-2848 > URL: https://issues.jboss.org/browse/JBDS-2848 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: usage > Reporter: Burr Sutter > Assignee: Andre Dietisheim > > We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage". > Areas worth tracking include (in priority order): > - Use of the OpenShift Wizard to successful completion vs error > - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8) > - Successful installation of the features found on Software/Update tab of JBoss Central > - Use of the JSF/RichFaces Visual Page Editor > - Use of the Hibernate Tooling > - Use of the jQuery Mobile Palette > - Use of BrowserSim > - Use of CordovaSim > We will also need to update http://www.jboss.org/tools/usage > Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool) > Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future. -- 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] (JBDS-2843) AngularJS Usability

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2843: -------------------------------------- Component/s: jsp/jsf/xml/html source editing > AngularJS Usability > ------------------- > > Key: JBDS-2843 > URL: https://issues.jboss.org/browse/JBDS-2843 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > > Related to JBIDE-14597 > Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML > Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code > Phase 3) Code Assist (cntrl-space) in .html > Phase 4) Code Assist (cntrl-space) in .js > Phase 5) Widget Palette (like our jQuery Mobile palete) -- 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