[JBoss JIRA] (JBDS-2853) HTML5 Client + Java EE 6 Server Project Sync/Link
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2853?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2853:
-------------------------------------------
Haven't we discussed this multiple times and come to the conclusion that these two are significantly different so it is point less ?
your cordova html app would be using cordova api - your server side html5 app would be using "pure" javascript.
This does not sound to me like a thing the tooling can handle - maybe some use of bower or other module/packaging system can be applied to make it so you can reuse larger parts of the code ?
> HTML5 Client + Java EE 6 Server Project Sync/Link
> -------------------------------------------------
>
> Key: JBDS-2853
> URL: https://issues.jboss.org/browse/JBDS-2853
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: aerogear-hybrid
> Reporter: Burr Sutter
>
> Related to
> https://issues.jboss.org/browse/JBIDE-14387
> https://issues.jboss.org/browse/JBDS-2735?focusedCommentId=12799277
> A typical HTML5 Client Project should be physically separated from the server-side Java EE 6 project (using JAX-RS, CDI, JPA, etc). Our current HTML5 archetype lays down a co-mingled project, this project can not be easily "imported" into a Hybrid/Cordova project. Can we find a solution that allows the end-user to more easily keep the client/server projects "in sync", where the client can be deployable to app stores via Cordova but is still testable/deployable as a mobile web app on EAP?
--
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, 4 months
[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:
-------------------------------------------
JBDS-2848 captures the "central" install part.
> 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: usage
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> 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
> 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, 4 months
[JBoss JIRA] (JBIDE-16241) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16241?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-16241:
-----------------------------------
Assignee: Fred Bricon
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Central]
> ------------------------------------------------------
>
> Key: JBIDE-16241
> URL: https://issues.jboss.org/browse/JBIDE-16241
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [Central]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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, 4 months
[JBoss JIRA] (JBDS-2850) JavaScript Editing Support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2850?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2850:
-------------------------------------------
[~burrsutter] Is that really the request ? looking for dynamic variables while in the IDE ? these are not possible to code complete without a running browser and knowing exactly which list of javascript and html files have been loaded.
I could imagine a bunch of other improvements to javascript editing support before doing this rather technical impossible one.
Like, support ecmascript 5, remove bogus valdations, code complete for actual static derivable javascript constructs (understanding function and object builders etc.)
> JavaScript Editing Support
> --------------------------
>
> Key: JBDS-2850
> URL: https://issues.jboss.org/browse/JBDS-2850
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
>
> 1) Support for code assist/completion (ctrl-space) for AngularJS $scope.
> 2) Support for code jQuery $('#
--
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, 4 months