April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-613) Document Using Maven

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-613?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-613: ------------------------------- Sprint: 2015/S10 (11-May -> 24-May) 2 (was: 2015/S9 (27-Apr > 10-May)) > Document Using Maven > -------------------- > > Key: TOOLSDOC-613 > URL: https://issues.jboss.org/browse/TOOLSDOC-613 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Misha Ali > Assignee: Misha Ali > Labels: maven > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-639) JBDS Tech Knowledge: Test all docs to better understand product and use cases by EOM (May)

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-639: ---------------------------------- Summary: JBDS Tech Knowledge: Test all docs to better understand product and use cases by EOM (May) Key: TOOLSDOC-639 URL: https://issues.jboss.org/browse/TOOLSDOC-639 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-621) Rework and Finalize Article about Generating a HTML5 Web App

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-621?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-621: ------------------------------------ I have added my edits directly into the text file (no images received) and sent the file back to Supriya. > Rework and Finalize Article about Generating a HTML5 Web App > ------------------------------------------------------------ > > Key: TOOLSDOC-621 > URL: https://issues.jboss.org/browse/TOOLSDOC-621 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Attachments: generate_HTML5_web_app.adoc > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Arun Gupta commented on JBIDE-18570: ------------------------------------ EJB 2.x labeling is fine for now. We can revisit if somebody else reports this. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-19716. ---------------------------------- Resolution: Rejected resolving. Len please open a new one to TOOLSDOC > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19719: -------------------------------------- I have removed the logging upstream > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19719: --------------------------------- Component/s: (was: aerogear-hybrid) > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19719: -------------------------------------- I do not see the purpose of tracing this one, I guess we can remove the logging if it is a bother. Warning is not needed either because as I have explained these are logged because of a chain of calls and we will ask user to fix the problem when it is a blocker > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-19727. ---------------------------------- Resolution: Duplicate Issue Duppos are great, gives a false sense of achievement :) > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19726: -------------------------------------- Yeah, we can not support 4.0.0 because cordova.js file has been relocated on the 4.0.0 distro. We have not run into this case because we had a white list of versions we can support in the past but with npm change that can not happen anymore. In any case, I will check and show a proper dialog for these cases. > Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta1 > > Attachments: IMG_2768.MOV > > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015