I will ask legal-discuss about the CSS content. I agree it is CC-BY-4.0.
I'm not sure about your interpretation of the rest though.
I don't share your concern about the images. I think the Royale project
chooses to trust the upstreams and not go on a witch-hunt, especially at
release time. MDL
Hi Piotr,
there's a maven command for "prepare release"[1] that changes all poms
automatically for you. It's the right way to do this task since is part of
the maven workflow. Updating poms to the next version manually could bring
many problems since is easy to forget some of them.
Thanks
[1]
+0 (Binding)
Maven Build compiler, typedefs and asjs - Pass.
Ant Build - Pass
Maven Artifacts and Ant binary IDE package checked with three examples
which are not part of the asjs respository.
I'm giving +0 because I couldn't build Maven binary distribution. It is
because poms from that folder
+1 Binding
Used Approval script (used playerglobal 11.1 swc)
I didn't see any problems that would withhold this from release.
‹peter
On 1/9/18, 11:25 AM, "yishayw" wrote:
>+1
>Package
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apac
-1 Binding
I ran the ApproveRoyale.xml script. The build failed for me here:
tests:
[mkdir] Created dir:
/Users/pent/temp/apache-royale-0.9.0-src/royale-compiler/compiler/target/ju
nit-reports
[mkdir] Created dir:
-1 Binding
* MD5 matches
* Signature valid
* README, RELEASE_NOTES, NOTICE and LICENSE look good
* Installation via NPM successful
* Able to cross-compile apps successfully with mxml from npm
* royale-compiler>mvn clean install -P -main,utils works fine
royale-compiler>mvn clean install
Unit
Hi,
This is vote for the 0.9.0 release of Apache Royale.
The release candidate can be found here;
https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/
Before voting please review the section,'What are the ASF requirements on
approving a release?', at: