[
https://issues.apache.org/jira/browse/GUACAMOLE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260174#comment-17260174
]
James Muehlner commented on GUACAMOLE-1085:
-------------------------------------------
Ah good, I stand corrected. My comments about needing to buy into
Babel/Webpack/Browserify were mistaken (which is good!).
I'd say that it looks like using ngUpgrade to upgrade the webapp piece by
piece, with both AngularJS and Angular components running in the same
application at the same time is the way to go, if possible. This approach
should allow dividing up the work of upgrading different parts of the app, and
ensuring that all changes are properly tested and released in a timely manner,
rather than trying to upgrade everything in one big push, flipping to the new
code at the end. (This is the approach we used when originally migrating to
AngularJS, and even with the much-smaller webapp at the time, it was a pain)
> Consider migrating web application from AngularJS
> -------------------------------------------------
>
> Key: GUACAMOLE-1085
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1085
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
> Reporter: Alfred Egger
> Priority: Major
>
> [AngularJS is in an LTS period until June 30,
> 2021|https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c].
> Unless resurrected as a community-driven project, it will be cease being
> maintained after that date. Assuming no such project surfaces, we should look
> into migrate the web application to another framework.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
