October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15750) AS7.1 requirement is not met when its downloaded and installed from IDE

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15750?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-15750: ------------------------------------- Attachment: HTML5_missing_req.png Fred, I can reproduce with HTML5 or any other (JEE6,Richfaces..). Try this: 1. open new workspace with no runtimes at all 2. open HTML5 wizard, AS requirement is not met 3. hit DOWNLOAD AND INSTALL (just INSTALL works ok) 4. after the AS7.1.1 is downloaded, requirement is still not met. You have to reopen the wizard again. See attached screenshot > AS7.1 requirement is not met when its downloaded and installed from IDE > ----------------------------------------------------------------------- > > Key: JBIDE-15750 > URL: https://issues.jboss.org/browse/JBIDE-15750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: HTML5_missing_req.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15750) AS7.1 requirement is not met when its downloaded and installed from IDE

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15750?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15750: ------------------------------------- Rastislav, I can't reproduce with the HTML5 wizard in central. Snjeza has a fix for regular examples (i.e. quickstarts). Can you please confirm? > AS7.1 requirement is not met when its downloaded and installed from IDE > ----------------------------------------------------------------------- > > Key: JBIDE-15750 > URL: https://issues.jboss.org/browse/JBIDE-15750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.1.1.Beta1 > > -- 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, 6 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15765: --------------------------------------------- [~ppalaga] I can't see that link. How can I get access ? [~bdaw] But the layering is the one that requires that your porduct slot should be jpp, not eap afaik. At least that is what the recognition is based on. Thus for me it looks like you moved *Away* from layering and back to bundle eap. Who from EAP suggested this change? > 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, 6 months

1
0
0 / 0

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

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi... ] Boleslaw Dawidowicz commented on JBIDE-15765: --------------------------------------------- We needed to change the way layering is done (not an add-on anymore). This was pointed out by EAP guys and needed to be compatible with patching mechanism in the future. I guess it can be the cause... > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15487) Export Native Platform Project is not working

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15487?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15487: ---------------------------------------- Priority: Blocker (was: Critical) > Export Native Platform Project is not working > --------------------------------------------- > > Key: JBIDE-15487 > URL: https://issues.jboss.org/browse/JBIDE-15487 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Alpha1 > Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > 1. Create new Mobile Hybrid Project. > 2. Select it and choose Export > Mobile > Export Native Platform Project > 3. Click Next > ERROR: Nothing happens > 4. Click Next Again > ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform" -- 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, 6 months

1
0
0 / 0

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

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi... ] Peter Palaga commented on JBIDE-15765: -------------------------------------- We did a couple of things: * We switched from EAP 6.1 to EAP 6.1.1 * [~mstruk] did "Package the portal using layers instead of add-ons" https://github.com/gatein-prod/gatein-portal/commit/698d096dbf340a3c8fa06... Does one of those explain it? > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15487) Export Native Platform Project is not working

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15487?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-15487: ----------------------------------------- I see the same issue as Vlado. > Export Native Platform Project is not working > --------------------------------------------- > > Key: JBIDE-15487 > URL: https://issues.jboss.org/browse/JBIDE-15487 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Alpha1 > Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.1.1.Beta1 > > > 1. Create new Mobile Hybrid Project. > 2. Select it and choose Export > Mobile > Export Native Platform Project > 3. Click Next > ERROR: Nothing happens > 4. Click Next Again > ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform" -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15300) Support signing when exporting mobile applications

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15300?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-15300: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > Support signing when exporting mobile applications > -------------------------------------------------- > > Key: JBIDE-15300 > URL: https://issues.jboss.org/browse/JBIDE-15300 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Priority: Minor > Fix For: 4.2.x > > > Mobile Application Export wizard does not produced signed binaries at this time. Support code signing of exported applications -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15486) Export Mobile Application dialog is not working

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15486?page=com.atlassian.jira.plugi... ] Michelle Murray edited comment on JBIDE-15486 at 10/25/13 12:37 AM: -------------------------------------------------------------------- I have the same issue as Vlado. There is no window asking you to select a platform. 1. Create new Mobile Hybrid Project. 2. Select it and choose Export > Mobile > Export Mobile Application 3. Click Next ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform" Running Fedora19, JBDS universal installer, Hybrid Mobile Tools 1.0.100.Beta1-v20131018-1426-B43 was (Author: mmurray): I have the same issue as Vlado. There is no window asking you to select a platform. 1. Create new Mobile Hybrid Project. 2. Select it and choose Export > Mobile > Export Mobile Application 3. Click Next ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform" > Export Mobile Application dialog is not working > ----------------------------------------------- > > Key: JBIDE-15486 > URL: https://issues.jboss.org/browse/JBIDE-15486 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Alpha1 > Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.1.1.Beta1 > > > 1. Create new Mobile Hybrid Project. > 2. Select it and choose Export > Mobile > Export Mobile Application > 3. Click Next > ERROR: Nothing happens > 4. Click Next Again > ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform" -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15486) Export Mobile Application dialog is not working

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15486?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-15486: ----------------------------------------- I have the same issue as Vlado. There is no window asking you to select a platform. 1. Create new Mobile Hybrid Project. 2. Select it and choose Export > Mobile > Export Mobile Application 3. Click Next ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform" > Export Mobile Application dialog is not working > ----------------------------------------------- > > Key: JBIDE-15486 > URL: https://issues.jboss.org/browse/JBIDE-15486 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Alpha1 > Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.1.1.Beta1 > > > 1. Create new Mobile Hybrid Project. > 2. Select it and choose Export > Mobile > Export Mobile Application > 3. Click Next > ERROR: Nothing happens > 4. Click Next Again > ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform" -- 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, 6 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