[JBoss JIRA] (JBIDE-16659) Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16659?page=com.atlassian.jira.plugi... ]
Vineet Reynolds updated JBIDE-16659:
------------------------------------
Description:
Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories.
When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode.
We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova platform add android}} + {{cordova prepare android}} or {{cordova platform add ios}} + {{cordova prepare ios}} group of commands that create the native SDK projects and update their contents.
was:
Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories.
When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode.
We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova prepare android}} or {{cordova prepare ios}} commands.
> Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16659
> URL: https://issues.jboss.org/browse/JBIDE-16659
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
>
> Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories.
> When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode.
> We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova platform add android}} + {{cordova prepare android}} or {{cordova platform add ios}} + {{cordova prepare ios}} group of commands that create the native SDK projects and update their contents.
--
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, 1 month
[JBoss JIRA] (JBIDE-16659) Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure
by Vineet Reynolds (JIRA)
Vineet Reynolds created JBIDE-16659:
---------------------------------------
Summary: Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure
Key: JBIDE-16659
URL: https://issues.jboss.org/browse/JBIDE-16659
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: aerogear-hybrid
Affects Versions: 4.1.1.Final
Reporter: Vineet Reynolds
Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories.
When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode.
We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova prepare android}} or {{cordova prepare ios}} commands.
--
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, 1 month
[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-15888 at 2/26/14 11:31 AM:
---------------------------------------------------------------
As discussed with [~burrsutter] on IRC, we'll wait for the WFK 2.5 archetype to be released before updating JBoss Central (this can be done after the JBT/JBDS builds)
[~jowilson], [~rafabene] do you guys confirm the next version will contain the RH Techpreview repository reference?
was (Author: fbricon):
As discussed with [~burrsutter] on IRC, we'll wait for the WFK 2.5 archetype to be released before updating JBoss Central (this can be done after the JBT/JBDS builds)
[~jowilson], [~rbenevides] do you guys confirm the next version will contain the RH Techpreview repository reference?
> Update the Spring Archetype reference
> -------------------------------------
>
> Key: JBIDE-15888
> URL: https://issues.jboss.org/browse/JBIDE-15888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Joshua Wilson
> Assignee: Fred Bricon
> Labels: spring
> Fix For: 4.1.2.Final
>
> Attachments: springmvc-test.xml
>
>
> I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version.
--
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, 1 month
[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15888:
-------------------------------------
As discussed with [~burrsutter] on IRC, we'll wait for the WFK 2.5 archetype to be released before updating JBoss Central (this can be done after the JBT/JBDS builds)
[~jowilson], [~rbenevides] do you guys confirm the next version will contain the RH Techpreview repository reference?
> Update the Spring Archetype reference
> -------------------------------------
>
> Key: JBIDE-15888
> URL: https://issues.jboss.org/browse/JBIDE-15888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Joshua Wilson
> Assignee: Fred Bricon
> Labels: spring
> Fix For: 4.1.2.Final
>
> Attachments: springmvc-test.xml
>
>
> I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version.
--
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, 1 month
[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2848:
-------------------------------------------
Currently the work happening here will make it possible for us to add events that will report things in form of:
category, action, label, value
we plan on having
category = component name
action = limited set of action types that can be reused across category/components(i.e. "new" will mean new artifact)
label = specific value (ie. type of action, i.e. which server type was created by new server
value = depend on context, but typically 1 = success 0 = failure or a value indicating number of times it will happen.
We would have direct events that happens on the fly to collect things like:
Which servers are a user creating succesfully:
example: ("server", "new", "org.jboss.tools.server.wtp_wildfly_8", 1)
which connector ids have been installed with success or failure
example: ("central", "install", "org.blah.egit", 1) (0 at end would mean failure)
These should be events that are "rare" so not for everytime you publish, but okey for everytime you create a server.
Other events would be collected through the day and only sent once a day or at startup time.
have a user used visual page editor
example: ("vpe", "editor", "<type>", 23) the 23 value here should be the number of times it was done since last report.
have a user used forge wizard
example: ("forge", "wizard", "<type>", 42) the 42 value here should be the number of times it was done since last report.
have a user used forge console:
example: ("forge", "console", "<type>", 42) the 42 value here should be the number of times it was done since last report.
This would be more often and something we would like to avoid sending all the time.
> Usage Stats for actual used features
> ------------------------------------
>
> Key: JBDS-2848
> URL: https://issues.jboss.org/browse/JBDS-2848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, usage
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: QE_JBDS80_needinfo
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.
--
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, 1 month
[JBoss JIRA] (JBDS-2844) Management API Server Adapter
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2844:
-------------------------------
Labels: (was: QE_JBDS80_needinfo)
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Minor
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
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, 1 month
[JBoss JIRA] (JBDS-2843) AngularJS Usability
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2843:
-------------------------------
CDW qa_ack: + (was: ?)
> AngularJS Usability
> -------------------
>
> Key: JBDS-2843
> URL: https://issues.jboss.org/browse/JBDS-2843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsp/jsf/xml/html source editing, requirements
> Reporter: Burr Sutter
>
> Related to JBIDE-14597
> Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
> Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
> Phase 3) Code Assist (cntrl-space) in .html
> Phase 4) Code Assist (cntrl-space) in .js
> Phase 5) Widget Palette (like our jQuery Mobile palete)
--
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, 1 month
[JBoss JIRA] (JBDS-2843) AngularJS Usability
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2843:
-----------------------------
CDW release: + (was: ?)
> AngularJS Usability
> -------------------
>
> Key: JBDS-2843
> URL: https://issues.jboss.org/browse/JBDS-2843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsp/jsf/xml/html source editing, requirements
> Reporter: Burr Sutter
>
> Related to JBIDE-14597
> Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
> Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
> Phase 3) Code Assist (cntrl-space) in .html
> Phase 4) Code Assist (cntrl-space) in .js
> Phase 5) Widget Palette (like our jQuery Mobile palete)
--
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, 1 month