April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11803) Include JBoss Java Formatter and Code cleanup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11803?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-11803: ----------------------------------- Fix Version/s: (was: 4.0.x) > Include JBoss Java Formatter and Code cleanup > --------------------------------------------- > > Key: JBIDE-11803 > URL: https://issues.jboss.org/browse/JBIDE-11803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Karel Piwko > Assignee: Max Rydahl Andersen > Fix For: LATER > > > It would be great if JBoss Java Code style formatter and code cleanup are installed out of the box in JBoss Tools. It is not required for them to be default, but user can select them easily. > Here are the sources: > https://github.com/jbossas/jboss-as/tree/master/ide-configs/eclipse > This would make developers using JBoss Tools produce properly formatted code an easier way. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13228) Support CDI 1.1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13228?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-13228. ------------------------------------ Fix Version/s: 4.2.0.Alpha1 (was: 4.2.0.Beta2) Resolution: Done > Support CDI 1.1 > --------------- > > Key: JBIDE-13228 > URL: https://issues.jboss.org/browse/JBIDE-13228 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > CDI 1.1 spec - http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html > The full list of changes in CDI 1.1 - https://issues.jboss.org/sr/jira.issueviews:searchrequest-printable/12314... -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6008) Warning if an @Constraint annotation does not have the expected @Retention policies (Bean Validation)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6008?page=com.atlassian.jira.plugin... ] Alexey Kazakov reassigned JBIDE-6008: ------------------------------------- Assignee: Alexey Kazakov > Warning if an @Constraint annotation does not have the expected @Retention policies (Bean Validation) > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-6008 > URL: https://issues.jboss.org/browse/JBIDE-6008 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi, hibernate > Reporter: Emmanuel Bernard > Assignee: Alexey Kazakov > Labels: integration > Fix For: LATER > > -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17002: ------------------------------------ Uh.... it was actually on/around 2014-03-18: http://download.jboss.org/jbosstools/static/releases/JBossTools-4.1.2.Fin... http://download.jboss.org/jbosstools/updates/stable/kepler/ http://tools.jboss.org/downloads/jbosstools/kepler/4.1.2.Final.html This connector is being added to the JBT 4.1.x Central site, AFTER JBT 4.1.2. Final; thus the name/version of that Central site would be 4.1.2.1.Final as it changes nothing in JBT 4.1.2 itself, and is only a single discovery plugin + xml file that gets amended to include the new connector. Surely you don't want me to call it 4.1.3? > Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2 > ----------------------------------------------------------- > > Key: JBIDE-17002 > URL: https://issues.jboss.org/browse/JBIDE-17002 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.2.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > Attachments: jbide17002-3-4-features.png, jbide17002-6-7-features.png, jbide17002-patch-catg.png > > > We decided to provide an easy way for JBT users to install Java 8 support in Eclipse Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP. > * JDT Feature patch : http://download.eclipse.org/eclipse/updates/4.3-P-builds/ > * M2E 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905 > * WTP Feature Patch : http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032... > All 3 features should be available via a unique connector in JBoss Central > Software Updates -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17174) "Run on Android emulator" fails for AVDs with Google APIs

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17174?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-17174: -------------------------------------- Seems like it was a problem with the command line parser. Fix dropped to master now. > "Run on Android emulator" fails for AVDs with Google APIs > --------------------------------------------------------- > > Key: JBIDE-17174 > URL: https://issues.jboss.org/browse/JBIDE-17174 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.0.Beta2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The build and deployment to an AVD with target "Google APIs (Google Inc.) - API Level X" fails with the following error message: > {noformat} > An internal error occurred during: "Launching Push-Demo (Android Emulator)". > For input string: "rget: Google APIs (Google Inc." > {noformat} > Recreating the AVD as a 'normal' one lacking Google APIs gets around this issue, but is not a suitable workaround for testing Cordova apps that depend on plugins requiring the Google APIs (like the Aerogear Push plugin that relies on GCM). Without the Google APIs, the GCM service intent will not be invoked, and thus apps will fail to register themselves against a Unified Push Server. > Additionally, the presence of this AVD prevents new Run configurations from being created or existing ones from being modified. Creating a new Android emulator configuration via {{Run -> Run As -> Run Configurations ...}} results in the same error. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17174) "Run on Android emulator" fails for AVDs with Google APIs

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17174?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-17174. ---------------------------------- Resolution: Done > "Run on Android emulator" fails for AVDs with Google APIs > --------------------------------------------------------- > > Key: JBIDE-17174 > URL: https://issues.jboss.org/browse/JBIDE-17174 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.0.Beta2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The build and deployment to an AVD with target "Google APIs (Google Inc.) - API Level X" fails with the following error message: > {noformat} > An internal error occurred during: "Launching Push-Demo (Android Emulator)". > For input string: "rget: Google APIs (Google Inc." > {noformat} > Recreating the AVD as a 'normal' one lacking Google APIs gets around this issue, but is not a suitable workaround for testing Cordova apps that depend on plugins requiring the Google APIs (like the Aerogear Push plugin that relies on GCM). Without the Google APIs, the GCM service intent will not be invoked, and thus apps will fail to register themselves against a Unified Push Server. > Additionally, the presence of this AVD prevents new Run configurations from being created or existing ones from being modified. Creating a new Android emulator configuration via {{Run -> Run As -> Run Configurations ...}} results in the same error. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17174) "Run on Android emulator" fails for AVDs with Google APIs

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17174?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-17174: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 4.2.0.Beta2 Assignee: Gorkem Ercan > "Run on Android emulator" fails for AVDs with Google APIs > --------------------------------------------------------- > > Key: JBIDE-17174 > URL: https://issues.jboss.org/browse/JBIDE-17174 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.0.Beta2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The build and deployment to an AVD with target "Google APIs (Google Inc.) - API Level X" fails with the following error message: > {noformat} > An internal error occurred during: "Launching Push-Demo (Android Emulator)". > For input string: "rget: Google APIs (Google Inc." > {noformat} > Recreating the AVD as a 'normal' one lacking Google APIs gets around this issue, but is not a suitable workaround for testing Cordova apps that depend on plugins requiring the Google APIs (like the Aerogear Push plugin that relies on GCM). Without the Google APIs, the GCM service intent will not be invoked, and thus apps will fail to register themselves against a Unified Push Server. > Additionally, the presence of this AVD prevents new Run configurations from being created or existing ones from being modified. Creating a new Android emulator configuration via {{Run -> Run As -> Run Configurations ...}} results in the same error. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-492: ------------------------------------- Summary: Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process) (was: migrate JBT User Guide to adoc so it's easier to maintain and can be reskinned to match new websiite) > Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process) > ------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-492 > URL: https://issues.jboss.org/browse/TOOLSDOC-492 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 4.2.0.Beta2 > > > With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc! > What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these: > http://tools.jboss.org/features/ (with icons that link to projects' latest doc) > or > http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked) > And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release. > Questions: > a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype) > b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1). > c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported? > d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming. > [0] https://github.com/oreillymedia/docbook2asciidoc > e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone? > [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... > f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]? > [2] http://tools.jboss.org/downloads/overview.html > [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-492) migrate JBT User Guide to adoc so it's easier to maintain and can be reskinned to match new websiite

by Nick Boldt (JIRA)

Nick Boldt created TOOLSDOC-492: ----------------------------------- Summary: migrate JBT User Guide to adoc so it's easier to maintain and can be reskinned to match new websiite Key: TOOLSDOC-492 URL: https://issues.jboss.org/browse/TOOLSDOC-492 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: User Guide Affects Versions: 4.2.0.Beta1 Reporter: Nick Boldt Assignee: Michelle Murray Fix For: 4.2.0.Beta2 With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc! What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these: http://tools.jboss.org/features/ (with icons that link to projects' latest doc) or http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked) And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release. Questions: a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype) b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1). c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported? d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming. [0] https://github.com/oreillymedia/docbook2asciidoc e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone? [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]? [2] http://tools.jboss.org/downloads/overview.html [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16756) Update Cordova version for XCode 5.1 compatibility

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16756?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16756: -------------------------------------- [~burrsutter], [~maxandersen] do we even have a 4.1.x release planned before 4.2.x? I think I will just reject this one. > Update Cordova version for XCode 5.1 compatibility > -------------------------------------------------- > > Key: JBIDE-16756 > URL: https://issues.jboss.org/browse/JBIDE-16756 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Priority: Minor > Fix For: 4.1.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Cordova version prior to version 3.5 are not compatible with XCode 5.1.. Upgrade Cordova shipped with 4.1.x for XCode 5.1 compatibility. > see http://shazronatadobe.wordpress.com/2014/03/12/xcode-5-1-and-cordova-ios/ for details -- 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

11 years, 11 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 April 2014