On Thu, Feb 2, 2017 at 2:50 PM, Luke Holmquist <lholmqui@redhat.com> wrote:I believe the UI was in its own repo during the first iteration(when it was ember :))yep, and it was a PITA to integrate the pure JS filesIf we want to attract contributors from the JS community, then making it a WAR is not really a great idea,sure, but... how useful is the UI outside of the context of push? and, bundling w/ push... perhaps we release it as NPM, and include that, somehow, into a WAR?
I see no other option for our deployment modelOn Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf <matzew@apache.org> wrote:separate repo, not sureseparate WAR file, I think at some point I want to have a bunch of different WAR files:* sender_API.war* registration_API.war* ui.warcore.jar (EJB w/ the messaging, as core)but, that's a bit in the future... we have some Swarm related JIRAs for thatOn Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett@redhat.com> wrote:______________________________Hello,Currently we have the UPS admin UI embedded into aerogear-unifiedpush-server project/repository.Could the admin-ui be a separated project (repository) with its own war file?While it may increase release process complexity (a new project dependency), I think it brings some benefits to the table, such as having a development cycle of this own, easier to write automated tests and easier to attract contributors from the javascript community (since we would be using common javascript tools to build it).WDYT?--_________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev --Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev --Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev