July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3085: ---------------------------------- That may be true but I know I click blindly through all kinds of warnings on Windows about upgrading crap like Flash player, Acrobat, anti-virus/anti-malware, hardware drivers, etc. Hell, I even blindly click thru the "fade screen and get Administrator permission" dialogs. So... are we sure we want to give users the option to break themselves irrevocably? Why not just give them TWO installers to choose from [1], which they can install separately to two different workspaces: [1] !http://snag.gy/w7HCy.jpg! > Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access? > --------------------------------------------------------------------------- > > Key: JBDS-3085 > URL: https://issues.jboss.org/browse/JBDS-3085 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Max brought up a question on a call today: > *Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?* > This was supposedly in the original scope for the creation of a Early Access site, but I never saw that. So, in order to get some eyeballs on this idea, and to get buy-in from QE/doc/dev/PM/PgM/PL, I'm cc:'ing some people here so we can discuss the cons and cons of this idea. > cc: [~mmusaji] [~mmurray] [~mmalina] [~maxandersen] [~mickael_istria][~ldimaggio] [~burrsutter] [~jpallich] [~rruss] [~fbricon] > (Aside: has anyone noticed that there's an plethora of people with "M" names on this team?) > Things to consider: > a) what happens if an 8.0.0.GA user suddenly finds they've updated to an Alpha or Beta release? Can they uninstall? (Probably not, if they started with the installer; probably yes if they started from BYOE / Marketplace.) > b) how will GSS support these "I was on GA but not I'm on Beta" users? > c) What about project examples that might / might not be compatible between 8.0 and 8.x, eg., because of changes in Eclipse Luna or a new default runtime (EAP 6.3, 6.4) ? > d) what could possibly go wrong? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-17728: ------------------------------------------ Attachment: scr.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png, IonicCheckbox.png, IonicCheckboxWizBan.png, IonicRadio.png, IonicRadioWizBan.png, IonicToggle.png, IonicToggleWizBan.png, List.png, ListWizBan.png, scr.png, Scroll.png, ScrollWizBan.png, SlideBox.png, SlideBoxWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17813) Update jQuery Mobile to the latest 1.4.3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17813?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17813: ----------------------------------- Description: Preferences - > JBoss Tools -> Web -> JS/CSS -> Restore Defaults (required for old workspaces) should add a new 1.4.3 JQM CSS/JS libs. New HTML File (JQM 1.4) template should also use 1.4.3 instead of 1.4.2 > Update jQuery Mobile to the latest 1.4.3 > ---------------------------------------- > > Key: JBIDE-17813 > URL: https://issues.jboss.org/browse/JBIDE-17813 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR1 > > > Preferences - > JBoss Tools -> Web -> JS/CSS -> Restore Defaults (required for old workspaces) should add a new 1.4.3 JQM CSS/JS libs. > New HTML File (JQM 1.4) template should also use 1.4.3 instead of 1.4.2 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17393) Show on main Central page the "Early Access" status

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17393?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-17393: ----------------------------------------- I don't think you should uninstall when disabling EA. I think that is frustrating to users - they might disable just for 10mins and then want to reenable and have to install stuff again. {quote} >'Early Access features installed but disabled I don't think it's explicit? What's disabled, the features or Early Access? {quote} I see 'EA features' as one thing so not sure how to answer that last one. I think I've missed something. For example, so a user turns on 'EA enabled' and then an example wizard might have EA items/actions/elements - and when turn EA off, the example wizard should revert back to being the non-EA version. Right? > Show on main Central page the "Early Access" status > --------------------------------------------------- > > Key: JBIDE-17393 > URL: https://issues.jboss.org/browse/JBIDE-17393 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: early-access > Fix For: 4.2.0.Beta3 > > > The main Central page (not Software one) should show the "Early Access" status. It can be one of > * No Early Access component installed, no Early Access enabled (shows nothing) > * No Early Access component installed, Early Access enabled (shows Early Access enabled) > * at least 1 Early Access component installed, Early Access Enabled > * at least 1 Early Access component installed, Early Access not Enabled -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-3085: --------------------------------------- +1 to [~mmusaji]'s reasoning; It seems a shame not to allow people to upgrade to a beta version if they are aware of the consequences - it's good to get users to use and review betas and this is a way to promote that. If we're going to allow it then I would suggest two pop-up warnings - the first is the standard are you sure you want to upgrade and the second is the 'WARNING!! you are moving to an unsupported version of JBDS and there is no undo - are you really sure you want to upgrade?' - 2 popups will certainly get people's attention and make them stop and think before blindly hitting the upgrade button. > Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access? > --------------------------------------------------------------------------- > > Key: JBDS-3085 > URL: https://issues.jboss.org/browse/JBDS-3085 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Max brought up a question on a call today: > *Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?* > This was supposedly in the original scope for the creation of a Early Access site, but I never saw that. So, in order to get some eyeballs on this idea, and to get buy-in from QE/doc/dev/PM/PgM/PL, I'm cc:'ing some people here so we can discuss the cons and cons of this idea. > cc: [~mmusaji] [~mmurray] [~mmalina] [~maxandersen] [~mickael_istria][~ldimaggio] [~burrsutter] [~jpallich] [~rruss] [~fbricon] > (Aside: has anyone noticed that there's an plethora of people with "M" names on this team?) > Things to consider: > a) what happens if an 8.0.0.GA user suddenly finds they've updated to an Alpha or Beta release? Can they uninstall? (Probably not, if they started with the installer; probably yes if they started from BYOE / Marketplace.) > b) how will GSS support these "I was on GA but not I'm on Beta" users? > c) What about project examples that might / might not be compatible between 8.0 and 8.x, eg., because of changes in Eclipse Luna or a new default runtime (EAP 6.3, 6.4) ? > d) what could possibly go wrong? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17813) Update jQuery Mobile to the latest 1.4.3

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-17813: -------------------------------------- Summary: Update jQuery Mobile to the latest 1.4.3 Key: JBIDE-17813 URL: https://issues.jboss.org/browse/JBIDE-17813 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.Beta3 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-17728: ---------------------------------- Attachment: SlideBoxWizBan.png SlideBox.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png, IonicCheckbox.png, IonicCheckboxWizBan.png, IonicRadio.png, IonicRadioWizBan.png, IonicToggle.png, IonicToggleWizBan.png, List.png, ListWizBan.png, Scroll.png, ScrollWizBan.png, SlideBox.png, SlideBoxWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-17728: ---------------------------------- Attachment: IonicToggleWizBan.png IonicToggle.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png, IonicCheckbox.png, IonicCheckboxWizBan.png, IonicRadio.png, IonicRadioWizBan.png, IonicToggle.png, IonicToggleWizBan.png, List.png, ListWizBan.png, Scroll.png, ScrollWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-17728: ---------------------------------- Attachment: IonicCheckboxWizBan.png IonicCheckbox.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png, IonicCheckbox.png, IonicCheckboxWizBan.png, IonicRadio.png, IonicRadioWizBan.png, List.png, ListWizBan.png, Scroll.png, ScrollWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17811) Incorrect bean injection eligibility assumption for beans excluded using DeltaSpike @Exclude

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17811?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17811: ----------------------------------- Fix Version/s: 4.2.0.CR1 > Incorrect bean injection eligibility assumption for beans excluded using DeltaSpike @Exclude > -------------------------------------------------------------------------------------------- > > Key: JBIDE-17811 > URL: https://issues.jboss.org/browse/JBIDE-17811 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions > Environment: JBDS 8.0.0.Beta2d > Reporter: Ron Šmeral > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.CR1 > > > With the following classes on the classpath: > {code:java|title=DeactivatableTest.java} > @Inject > private MyBean myBean; > {code} > {code:java|title=MyBean.java} > @Exclude > public class MyBean {} > {code} > {code:java|title=ExcludeExtensionDeactivator.java} > public class ExcludeExtensionDeactivator implements ClassDeactivator { > public Boolean isActivated(Class<? extends Deactivatable> targetClass { > if (ExcludeExtension.class.equals(targetClass)) { > return false; > } > return null; > } > } > {code} > ..the injection point in DeactivatableTest is marked with a warning: > {noformat} > No bean is eligible for injection to the injection point [JSR-299 §5.2.1] {noformat} > ..which is incorrect. MyBean *is* eligible despite being annotated @Exclude, since ExcludeExtension is deactivated using the core DeltaSpike mechanism of deactivation (ClassDeactivator). > There does not seem to be a (simple) solution to this other than executing the code in all available ClassDeactivators. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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