[jira] [Closed] (WEEX-34) Update csslayout to Yoga

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-34.
-
Resolution: Won't Fix

No need to upgrade Yoga anymore

> Update csslayout to Yoga
> 
>
> Key: WEEX-34
> URL: https://issues.apache.org/jira/browse/WEEX-34
> Project: Weex
>  Issue Type: Task
>Reporter: sospartan
>
> Weex bundle old csslayout source code, which is out of date.
> The library is renamed to 'yoga'.
> In android side, it's provided jcenter artifacts:
> > https://bintray.com/facebook/maven/com.facebook.yoga%3Ayoga
> latest version is 1.4.2
> After change to remote dependency, source code under 
> 'android/sdk/src/main/java/com/taobao/weex/dom/flex' could be removed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-67) ios SDK 0.13.0

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-67.
---
Resolution: Fixed

> ios SDK 0.13.0
> --
>
> Key: WEEX-67
> URL: https://issues.apache.org/jira/browse/WEEX-67
> Project: Weex
>  Issue Type: Bug
>Reporter: Mr.Dragonn
>Assignee: sospartan
> Attachments: 2621772495-599fbe19b5b07_articlex.png
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> ios SDK升级到0.13.0以后 运行程序就会报错 
> 我们项目是从weex0.3.0的版本就开始用,当时还不支持cocoapods 所以只能在本地通过
> pod 'WeexSDK', :path=>'./sdk/'
> 引用 
> 而且我们还在原来的SDK基础上做了一些改动(例如text选中动画效果等...),所以需要用到SDK中的源文件,现在直接使用cocoapods来引用的时候开放出来的头文件中没有我们进行修改的头文件.在0.12.0版本以前我们还是将SDK文件下载到本地
>  然后引入到工程来使用,但是在0.13.0开始,引入SDK后就出现各种错误
> 现在下载0.16.0引入到项目中
> 执行pod 'WeexSDK', :path=>'./sdk/' 
> 结果文件夹下没有weex文件



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-64) Upgrade to API 25

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-64:
-

Assignee: Adam Feng  (was: sospartan)

> Upgrade to API 25
> -
>
> Key: WEEX-64
> URL: https://issues.apache.org/jira/browse/WEEX-64
> Project: Weex
>  Issue Type: New Feature
>Reporter: YorkShen
>Assignee: Adam Feng
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-64) Upgrade to API 25

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-64.
---
Resolution: Fixed

> Upgrade to API 25
> -
>
> Key: WEEX-64
> URL: https://issues.apache.org/jira/browse/WEEX-64
> Project: Weex
>  Issue Type: New Feature
>Reporter: YorkShen
>Assignee: Adam Feng
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-74) commit-msg in git hook should allow user to submit commit with title [WEEX-xxx]

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-74:
-

Assignee: (was: sospartan)

> commit-msg in git hook should allow user to submit commit with title 
> [WEEX-xxx]
> ---
>
> Key: WEEX-74
> URL: https://issues.apache.org/jira/browse/WEEX-74
> Project: Weex
>  Issue Type: Improvement
>  Components: Project 
>Reporter: Jonathan Dong
>Priority: Minor
>
> According to the current commit log policy, people can only submit commit 
> with the title:
> {action} [{module}] {description}
> more details can be found 
> [here](https://github.com/apache/incubator-weex/blob/master/CONTRIBUTING.md#commit-log)
> As we decided to re-adopt Apache's Jira to track project's bugs and features, 
> we hope we can use the auto-correlation feature to automatically connect 
> commit with Jira issue by setting your commit log title with "[WEEX-xxx] 
> ". So it is needed to change the commit-msg git hook.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-74) commit-msg in git hook should allow user to submit commit with title [WEEX-xxx]

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-74.
---
Resolution: Fixed

> commit-msg in git hook should allow user to submit commit with title 
> [WEEX-xxx]
> ---
>
> Key: WEEX-74
> URL: https://issues.apache.org/jira/browse/WEEX-74
> Project: Weex
>  Issue Type: Improvement
>  Components: Project 
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>
> According to the current commit log policy, people can only submit commit 
> with the title:
> {action} [{module}] {description}
> more details can be found 
> [here](https://github.com/apache/incubator-weex/blob/master/CONTRIBUTING.md#commit-log)
> As we decided to re-adopt Apache's Jira to track project's bugs and features, 
> we hope we can use the auto-correlation feature to automatically connect 
> commit with Jira issue by setting your commit log title with "[WEEX-xxx] 
> ". So it is needed to change the commit-msg git hook.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-74) commit-msg in git hook should allow user to submit commit with title [WEEX-xxx]

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-74:
-

Assignee: Adam Feng

> commit-msg in git hook should allow user to submit commit with title 
> [WEEX-xxx]
> ---
>
> Key: WEEX-74
> URL: https://issues.apache.org/jira/browse/WEEX-74
> Project: Weex
>  Issue Type: Improvement
>  Components: Project 
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>
> According to the current commit log policy, people can only submit commit 
> with the title:
> {action} [{module}] {description}
> more details can be found 
> [here](https://github.com/apache/incubator-weex/blob/master/CONTRIBUTING.md#commit-log)
> As we decided to re-adopt Apache's Jira to track project's bugs and features, 
> we hope we can use the auto-correlation feature to automatically connect 
> commit with Jira issue by setting your commit log title with "[WEEX-xxx] 
> ". So it is needed to change the commit-msg git hook.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-72) English document in "Set Up Development Environment" need to be updated

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-72:
-

Assignee: Adam Feng  (was: sospartan)

> English document in "Set Up Development Environment" need to be updated
> ---
>
> Key: WEEX-72
> URL: https://issues.apache.org/jira/browse/WEEX-72
> Project: Weex
>  Issue Type: Bug
>  Components: Project 
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>  Labels: easyfix
>
> The English version of the document "Set Up Development Environment" has some 
> grammar glitches, the "dotWe" link at the bottom is not accessible. 
> Document URL: http://weex-project.io/guide/set-up-env.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-72) English document in "Set Up Development Environment" need to be updated

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-72.
---
Resolution: Fixed

> English document in "Set Up Development Environment" need to be updated
> ---
>
> Key: WEEX-72
> URL: https://issues.apache.org/jira/browse/WEEX-72
> Project: Weex
>  Issue Type: Bug
>  Components: Project 
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>  Labels: easyfix
>
> The English version of the document "Set Up Development Environment" has some 
> grammar glitches, the "dotWe" link at the bottom is not accessible. 
> Document URL: http://weex-project.io/guide/set-up-env.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-76) Update "Set Up Development Environment" English Document

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-76.
---
Resolution: Fixed

> Update "Set Up Development Environment" English Document
> 
>
> Key: WEEX-76
> URL: https://issues.apache.org/jira/browse/WEEX-76
> Project: Weex
>  Issue Type: Bug
>  Components: Project 
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>
> The English version of the document "Setup development environment" needs to 
> be updated for some grammar and expression glitches.
> Document URL: http://weex-project.io/guide/set-up-env.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-76) Update "Set Up Development Environment" English Document

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-76:
-

Assignee: Adam Feng  (was: sospartan)

> Update "Set Up Development Environment" English Document
> 
>
> Key: WEEX-76
> URL: https://issues.apache.org/jira/browse/WEEX-76
> Project: Weex
>  Issue Type: Bug
>  Components: Project 
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>
> The English version of the document "Setup development environment" needs to 
> be updated for some grammar and expression glitches.
> Document URL: http://weex-project.io/guide/set-up-env.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-19) Weex(iOS),If want to let the frame adjust content's height, you need set frame(0, 0, width, NAN), but it sometime will crash

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-19:
-

Assignee: xingZhang

> Weex(iOS),If want to let the frame adjust content's height, you need set 
> frame(0, 0, width, NAN), but it sometime will crash
> 
>
> Key: WEEX-19
> URL: https://issues.apache.org/jira/browse/WEEX-19
> Project: Weex
>  Issue Type: Bug
> Environment: iOS
>Reporter: yuedong
>Assignee: xingZhang
>
> - (void)setFrame:(CGRect)frame
> {
> if (!CGRectEqualToRect(frame, _frame)) {
> _frame = frame;
> WXPerformBlockOnMainThread(^{
> if (_rootView) {
> _rootView.frame = frame;
> WXPerformBlockOnComponentThread(^{
> [self.componentManager rootViewFrameDidChange:frame];
> });
> }
> });
> }
> }
> if the _rootView is not nil, the frame(0, 0, width, NAN) will direct set to 
> _rootView, then will crash.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-31) weex support Event Bubbling

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-31.
---
Resolution: Fixed

> weex support Event Bubbling
> ---
>
> Key: WEEX-31
> URL: https://issues.apache.org/jira/browse/WEEX-31
> Project: Weex
>  Issue Type: New Feature
> Environment: iOS, Android, HTML5
>Reporter: Tianyi Ma
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> This version will follow the W3C standard to implement event bubbling.
> Before: jsfm receives the event after the fireEvent event, which triggers the 
> corresponding element binding.
> After: jsfm receive fireEvent event, it will trigger the corresponding 
> element of the event handler, and the event back to the root component 
> recursive, triggering the path of all binding handler node.
> To terminate the bubbling behavior: In the handler for the node on the path, 
> write el.stopPropagation() to prevent further delivery.
> For forward compatibility, the bubbling mechanism is not turned on by 
> default. If you want to use it, you can open it in the configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-28) Component height animation not properly

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-28:
-

Assignee: Adam Feng

> Component height animation not properly
> ---
>
> Key: WEEX-28
> URL: https://issues.apache.org/jira/browse/WEEX-28
> Project: Weex
>  Issue Type: Bug
> Environment: Android, iOS
>Reporter: moxun
>Assignee: Adam Feng
>
> There are two issues with animation:
> Issue1 for iOS:
> The pivot of animation is the center of component instead of top.
> demo: http://dotwe.org/weex/4a14b70cb38e7a4e249ef8c983c6d1cb
> expect: the default pivot is the top of component
> Issue2 for Android and iOS:
> The container size does not vary with the size of the content.
> demo: http://dotwe.org/weex/539606f1a765742f492994415d419d0c 
> except: the container size increases or decreases as the content size



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-28) Component height animation not properly

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-28.
---
Resolution: Fixed

> Component height animation not properly
> ---
>
> Key: WEEX-28
> URL: https://issues.apache.org/jira/browse/WEEX-28
> Project: Weex
>  Issue Type: Bug
> Environment: Android, iOS
>Reporter: moxun
>Assignee: Adam Feng
>
> There are two issues with animation:
> Issue1 for iOS:
> The pivot of animation is the center of component instead of top.
> demo: http://dotwe.org/weex/4a14b70cb38e7a4e249ef8c983c6d1cb
> expect: the default pivot is the top of component
> Issue2 for Android and iOS:
> The container size does not vary with the size of the content.
> demo: http://dotwe.org/weex/539606f1a765742f492994415d419d0c 
> except: the container size increases or decreases as the content size



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-27) Prerender

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-27:
-

Assignee: Adam Feng

> Prerender
> -
>
> Key: WEEX-27
> URL: https://issues.apache.org/jira/browse/WEEX-27
> Project: Weex
>  Issue Type: New Feature
> Environment: Android, iOS, (not Html5)
>Reporter: xingjiu
>Assignee: Adam Feng
> Attachments: TB12RlEQFccXFXX.jpg
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> In order to impove the page open speed, we have intro many ways, such as 
> js-bundle prefetch.
> Now we have a new idea of render the next page in background. When click the 
> button to jump to the next page, just show it, no other js file execute cost 
> needed.
> We call it prerender.
> First. Limition
> Prerender will benifit user experience of waiting time of new page load.
> It is like a tradition way, use extre space(memory) to reduce time cost.
> We need to protected our app`s memory cost, so just one page can be 
> prerendered. This limit maybe removed later.
> Second. How we do?
> One way is to store the callNative commander in memory.
> We know weex use javascript engine to explain how the page will be render, 
> then js will use callNative() to make native views created.
> Once we just store the callNative commander, not to execute it. When the page 
> is truely show, do the commander executed.
> The attach image is the order of weex render steps currently.
> Finally. 
> Our goal is to make weex page show quickly.
> We assure that using prerender, the page open in one second will reach 99.9+ 
> precent. And the global festive main page will works prefect in prerender 
> mode.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-43) Add release job to travis CI

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-43:
-

Assignee: Adam Feng  (was: sospartan)

> Add release job to travis CI
> 
>
> Key: WEEX-43
> URL: https://issues.apache.org/jira/browse/WEEX-43
> Project: Weex
>  Issue Type: Task
>  Components: Project 
>Reporter: sospartan
>Assignee: Adam Feng
>
> Some changes will make to project's travis config:   
> * Put commands to `.travis` config use `if` statement, avoid using script 
> file will make more easier to determine problems.
> * Add our release test
>   * Create a release source tarball
>   * test build script for source release
>   * upload daily build artfacts (This will wait until we add snapshot upload 
> script)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (WEEX-36) Fix problems in 0.12 RC3

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-36:
-

Assignee: Adam Feng  (was: sospartan)

> Fix problems in 0.12 RC3
> 
>
> Key: WEEX-36
> URL: https://issues.apache.org/jira/browse/WEEX-36
> Project: Weex
>  Issue Type: Task
>  Components: Project 
>Reporter: sospartan
>Assignee: Adam Feng
> Fix For: 0.12
>
>
> In RC3 vote, Craig point out we have lots issue of the source tarball. 
> So I'll explain these problems one by one.
> {quote}
> > I also must vote -1 on this release.
> > 
> > clr% find . -name "*.jar"
> > ./android/playground/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/license/license-gradle-plugin-0.12.1.jar
> > ./android/sdk/license/maven-license-plugin-1.10.b1.jar
> > ./android/sdk/license/plexus-utils-3.0.24.jar
> > ./android/weex_debug/gradle/wrapper/gradle-wrapper.jar
> > ./android/weex_debug/libs/classes.jar
> > ./scripts/apache-rat-0.12.jar
> > 
> > 1. These jar files are not source and must not appear in the source release.
> > 
> {quote}
> These files were excluded from release. Some of them were replaced with maven 
> dependencies in SDK(android/sdk).
> {quote}
> > 2. I appreciate the effort involved in compiling the 
> > POSSIBLE-NOTICES-FOR-BIN-DIST. But looking into these dependencies I am > 
> > troubled by the difficulty actually finding the licenses of the projects.
> > 
> > For example, the "possible notice" for animaitonjs (possible typo here) 
> > refers to https://www.npmjs.com/package/animationjs from > which it is 
> > impossible (ok, perhaps possible but I could not find a link)  to find the 
> > actual project.
> > 
> > References to npmjs in this entire file should be removed and replaced by 
> > references to the home of the project. (Not relevant > for this release 
> > because the files are not actually being distributed.)
> > 
> {quote}
> The projects' link were all fixed.
> {quote}
> > 3. The java source files in android/commons/src are still in the 
> > com.alibaba name space. Assuming that these are actually weex > source 
> > files, they must be repackaged to org.apache.
> > 
> {quote}
> Package name is now 'org.apache'. I'll use a script to update the package 
> name when release.
> {quote}
> > 4. The javascript source files in playground/app/src are missing the 
> > license header. They have a style that I do not recognize. > Are these 
> > generated files?  The first several lines of storage-demo.js:
> > 
> > /**/ (function(modules) { // webpackBootstrap
> > /**/// The module cache
> > /**/var installedModules = {};
> > 
> > /**/// The require function
> > /**/function __webpack_require__(moduleId) {
> > 
> > /**/// Check if module is in cache
> > /**/if(installedModules[moduleId])
> > /**/return installedModules[moduleId].exports;
> > 
> {quote}
> These pre-build files were excluded. README_RELEASE will tell you to build 
> weex from ground.
> {quote}
> > 5. The java files in playground/app/src/main/java_zxing are in the 
> > com.google name space. They have a google license header.
> > 
> {quote}
> The 'playground' sample project was excluded, so were these files.
> {quote}
> > 6. The packages/weex-html5 contains LICENSE and NOTICE files. These should 
> > be in the top level directory of the release.
> > 
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 7. The scripts/rh contains LICENSE and NOTICE files. These should be in the 
> > top level directory of the release.
> > 
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 8. There is an executable file that doesn't belong:
> > 
> > clr% ls -l start
> > -rwxr-xr-x@ 1 clr  staff  161 Apr 27 20:34 start
> > 
> {quote}
> These files were excluded, not using to build weex SDK. It's just some 
> utility script in development.
> {quote}
> > 9. There is an executable gradlew in sdk/gradle that doesn't belong in a 
> > source release.
> > 
> {quote}
> Excluded. You can use your installed gradle to set this up.
> {quote}
> > 10. There are shared objects in sdk/libs that don't belong in a source 
> > release.
> > 
> {quote}
> Excluded. They are download during build.
> {quote}
> > 11. There are NOTICE and LICENSE files in ios/sdk that seem to be unix 
> > executable files.
> > 
> > clr% ls -l ios/sdk
> > total 40
> > -rwxr-xr-x@  1 clr  staff  11343 Apr 27 20:34 LICENSE
> > -rwxr-xr-x@  1 clr  staff575 Apr 27 20:34 NOTICE
> > 
> {quote}
> Removed from project. It's a left-over.
> {quote}
> > 12. The README.md doesn't tell me how to build/use org.apache.weex. The 
> > first several lines refer to third-party projects fro

[jira] [Assigned] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-44:
-

Assignee: Adam Feng  (was: sospartan)

> Add script to upload snapshot artifact to maven/pods repo
> -
>
> Key: WEEX-44
> URL: https://issues.apache.org/jira/browse/WEEX-44
> Project: Weex
>  Issue Type: Sub-task
>  Components: Project 
>Reporter: sospartan
>Assignee: Adam Feng
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (WEEX-36) Fix problems in 0.12 RC3

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-36.
---
Resolution: Fixed

> Fix problems in 0.12 RC3
> 
>
> Key: WEEX-36
> URL: https://issues.apache.org/jira/browse/WEEX-36
> Project: Weex
>  Issue Type: Task
>  Components: Project 
>Reporter: sospartan
>Assignee: Adam Feng
> Fix For: 0.12
>
>
> In RC3 vote, Craig point out we have lots issue of the source tarball. 
> So I'll explain these problems one by one.
> {quote}
> > I also must vote -1 on this release.
> > 
> > clr% find . -name "*.jar"
> > ./android/playground/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/license/license-gradle-plugin-0.12.1.jar
> > ./android/sdk/license/maven-license-plugin-1.10.b1.jar
> > ./android/sdk/license/plexus-utils-3.0.24.jar
> > ./android/weex_debug/gradle/wrapper/gradle-wrapper.jar
> > ./android/weex_debug/libs/classes.jar
> > ./scripts/apache-rat-0.12.jar
> > 
> > 1. These jar files are not source and must not appear in the source release.
> > 
> {quote}
> These files were excluded from release. Some of them were replaced with maven 
> dependencies in SDK(android/sdk).
> {quote}
> > 2. I appreciate the effort involved in compiling the 
> > POSSIBLE-NOTICES-FOR-BIN-DIST. But looking into these dependencies I am > 
> > troubled by the difficulty actually finding the licenses of the projects.
> > 
> > For example, the "possible notice" for animaitonjs (possible typo here) 
> > refers to https://www.npmjs.com/package/animationjs from > which it is 
> > impossible (ok, perhaps possible but I could not find a link)  to find the 
> > actual project.
> > 
> > References to npmjs in this entire file should be removed and replaced by 
> > references to the home of the project. (Not relevant > for this release 
> > because the files are not actually being distributed.)
> > 
> {quote}
> The projects' link were all fixed.
> {quote}
> > 3. The java source files in android/commons/src are still in the 
> > com.alibaba name space. Assuming that these are actually weex > source 
> > files, they must be repackaged to org.apache.
> > 
> {quote}
> Package name is now 'org.apache'. I'll use a script to update the package 
> name when release.
> {quote}
> > 4. The javascript source files in playground/app/src are missing the 
> > license header. They have a style that I do not recognize. > Are these 
> > generated files?  The first several lines of storage-demo.js:
> > 
> > /**/ (function(modules) { // webpackBootstrap
> > /**/// The module cache
> > /**/var installedModules = {};
> > 
> > /**/// The require function
> > /**/function __webpack_require__(moduleId) {
> > 
> > /**/// Check if module is in cache
> > /**/if(installedModules[moduleId])
> > /**/return installedModules[moduleId].exports;
> > 
> {quote}
> These pre-build files were excluded. README_RELEASE will tell you to build 
> weex from ground.
> {quote}
> > 5. The java files in playground/app/src/main/java_zxing are in the 
> > com.google name space. They have a google license header.
> > 
> {quote}
> The 'playground' sample project was excluded, so were these files.
> {quote}
> > 6. The packages/weex-html5 contains LICENSE and NOTICE files. These should 
> > be in the top level directory of the release.
> > 
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 7. The scripts/rh contains LICENSE and NOTICE files. These should be in the 
> > top level directory of the release.
> > 
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 8. There is an executable file that doesn't belong:
> > 
> > clr% ls -l start
> > -rwxr-xr-x@ 1 clr  staff  161 Apr 27 20:34 start
> > 
> {quote}
> These files were excluded, not using to build weex SDK. It's just some 
> utility script in development.
> {quote}
> > 9. There is an executable gradlew in sdk/gradle that doesn't belong in a 
> > source release.
> > 
> {quote}
> Excluded. You can use your installed gradle to set this up.
> {quote}
> > 10. There are shared objects in sdk/libs that don't belong in a source 
> > release.
> > 
> {quote}
> Excluded. They are download during build.
> {quote}
> > 11. There are NOTICE and LICENSE files in ios/sdk that seem to be unix 
> > executable files.
> > 
> > clr% ls -l ios/sdk
> > total 40
> > -rwxr-xr-x@  1 clr  staff  11343 Apr 27 20:34 LICENSE
> > -rwxr-xr-x@  1 clr  staff575 Apr 27 20:34 NOTICE
> > 
> {quote}
> Removed from project. It's a left-over.
> {quote}
> > 12. The README.md doesn't tell me how to build/use org.apache.weex. The 
> > first several lines refer to third-party projects from > Alibaba and 
> > coco

[jira] [Resolved] (WEEX-60) support perspective for rotate in 3d dimension

2017-10-06 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-60.
---
Resolution: Fixed

> support perspective for rotate in 3d dimension
> --
>
> Key: WEEX-60
> URL: https://issues.apache.org/jira/browse/WEEX-60
> Project: Weex
>  Issue Type: New Feature
>Reporter: xingZhang
>Assignee: xingZhang
>
> iOS Android and html5 will support  a new feature about perspective function 
> in transform when making rotation in 3d dimension according to the w3c 
> description 
> [here](https://developer.mozilla.org/en-US/docs/Web/CSS/perspective)
> the default value of perspective function is +inf , thus it will be parallel 
> projection. 
> perspective function can be  the following value:
>perspective(20px)
> note: the function must be the first one in transform
> other case will be invalid.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)