You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@senssoft.apache.org by "Alex Ford (JIRA)" <ji...@apache.org> on 2017/06/14 18:07:00 UTC
[jira] [Resolved] (SENSSOFT-175) Integrate web extension with
existing User ALE build process
[ https://issues.apache.org/jira/browse/SENSSOFT-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Ford resolved SENSSOFT-175.
--------------------------------
Resolution: Implemented
Running the build for userale.js should now bundle the web extension into the ./build/ directory. It must be used out of this directory now. The web extension source code and other artifacts have been moved into a folder under userale.js' src folder. The web extension README.md has been updated with new instructions and commands.
> Integrate web extension with existing User ALE build process
> ------------------------------------------------------------
>
> Key: SENSSOFT-175
> URL: https://issues.apache.org/jira/browse/SENSSOFT-175
> Project: SensSoft
> Issue Type: Improvement
> Components: UserALE.js
> Reporter: Alex Ford
> Assignee: Alex Ford
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The web extension currently relies on a copy of the User ALE client script that is checked into source control. As we integrate the web extension into the main User ALE build, there are opportunities to remove things like this. Have it so that when User ALE is built, the current version of the script is made available to the web extension plugin. Explore other integration opportunities as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)