[JBoss JIRA] (JBIDE-16064) org.jboss.tools.vpe.cordovasim.feature should be labelled "Technology Preview", not "Experimental"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16064?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16064:
-------------------------------
Description:
In JBDS-2821, [~maxandersen] decided that the org.jboss.tools.vpe.cordovasim.feature feature should be "Technology Preview", not "Experimental".
Connector Certification Definitions are here: https://devstudio.jboss.com/updates/7.0-development/central/
was:
In JBDS-2821, [~maxandersen] decided that the org.jboss.tools.vpe.cordovasim.feature feature should be "Technology Preview", not "Experimental".
> org.jboss.tools.vpe.cordovasim.feature should be labelled "Technology Preview", not "Experimental"
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16064
> URL: https://issues.jboss.org/browse/JBIDE-16064
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.1.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> In JBDS-2821, [~maxandersen] decided that the org.jboss.tools.vpe.cordovasim.feature feature should be "Technology Preview", not "Experimental".
> Connector Certification Definitions are here: https://devstudio.jboss.com/updates/7.0-development/central/
--
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, 5 months
[JBoss JIRA] (JBIDE-16065) JBoss Mobile Hybrid should be labelled "Technology Preview", not "Experimental"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16065:
-------------------------------
Description:
In JBDS-2821, [~maxandersen] decided that the JBoss Mobile Hybrid features should be "Technology Preview", not "Experimental".
Connector Certification Definitions are here: https://devstudio.jboss.com/updates/7.0-development/central/
was:
In JBDS-2821, [~maxandersen] decided that the JBoss Mobile Hybrid features should be "Technology Preview", not "Experimental".
> JBoss Mobile Hybrid should be labelled "Technology Preview", not "Experimental"
> -------------------------------------------------------------------------------
>
> Key: JBIDE-16065
> URL: https://issues.jboss.org/browse/JBIDE-16065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.1.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> In JBDS-2821, [~maxandersen] decided that the JBoss Mobile Hybrid features should be "Technology Preview", not "Experimental".
> Connector Certification Definitions are here: https://devstudio.jboss.com/updates/7.0-development/central/
--
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, 5 months
[JBoss JIRA] (JBIDE-16065) JBoss Mobile Hybrid should be labelled "Technology Preview", not "Experimental"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16065:
-------------------------------
Description:
In JBDS-2821, [~maxandersen] decided that the JBoss Mobile Hybrid features should be "Technology Preview", not "Experimental".
was:
In JBDS-2821, [~maxandersen] decided that the org.jboss.tools.vpe.cordovasim.feature feature should be "Technology Preview", not "Experimental".
> JBoss Mobile Hybrid should be labelled "Technology Preview", not "Experimental"
> -------------------------------------------------------------------------------
>
> Key: JBIDE-16065
> URL: https://issues.jboss.org/browse/JBIDE-16065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.1.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> In JBDS-2821, [~maxandersen] decided that the JBoss Mobile Hybrid features should be "Technology Preview", not "Experimental".
--
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, 5 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Sande Gilda (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Sande Gilda commented on JBDS-2727:
-----------------------------------
[~vineet.reynolds]: I will look and see if I can figure it out.
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 7.1.0.GA
>
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
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, 5 months
[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-16063:
-------------------------------
Assignee: Koen Aers
> Aborting a command has strange behavior
> ----------------------------------------
>
> Key: JBIDE-16063
> URL: https://issues.jboss.org/browse/JBIDE-16063
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
> Attachments: forge-screen-1.png, forge-screen-2.png
>
>
> I see 2 problems how aborting a command currently works.
> * If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot:
> !forge-screen-1.png!
> * Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error.
> !forge-screen-2.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, 5 months