Hi Alex,
I know tha batch file does not change but the jar inside. I was
expecting that the batch file points to the latest jar generated in
somewhere in one of three repos.
Let me make it clear. I am happy with building framework with maven
and building my project with ant.
I understand that you advise me to choose all-maven or or-ant but i do
not think it is neccessary, spesifically for my own project.
I just need to know the place of the compiler-jar in the repo after
building all three repositories with maven locally rather than
donwloading the nigtly builds.
Simply, as a summary i would like to know how can i generate nightly
build on my local environment ?:)
if yes, then it solves all my problems, if no than it is better to
wait for the nightly build to be available with latest commits.
Any advice appreciated.
Thanks,
Serkan
Alinti Alex Harui <[email protected]>
I don’t think mxmlc.bat has changed.
I think you are using some unusual workflow, using Maven to build
SWC and then referencing them from the command-line instead of using
Maven to build the app. IMO, it would be better for you to choose
Maven or not-Maven (Ant and command-line) so you are using one of
our supported workflows, and then we will have a better idea of how
to answer questions like this.
My 2 cents,
-Alex
From: Serkan Taş <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Tuesday, November 27, 2018 at 1:34 PM
To: "[email protected]" <[email protected]>
Subject: Re: build is broken : royale-asjs, mxroyale, sparkroyale
Hi Alex,
running mvn sequentially for royale-compiler, royale-typedefs-,
royale-asjs builds are fixed.
For the latest downloaded release i was using
apache-royale-0.9.5-bin-js-swf\royale-asjs\js\bin\mxmlc.bat for build.
Which file should i use from repos ?
Thanks,
Serkan
27.11.2018 23:58 tarihinde Alex Harui yazdı:
I should really have written: “the latest development version”.
The latest released version will be publicly available.
The CI server got stuck somehow. We’ll see if the next build works.
Looks like it takes an hour or so on the CI server. Building them
yourself should be faster.
-Alex
From: Alex Harui <[email protected]><mailto:[email protected]>
Reply-To: "[email protected]"<mailto:[email protected]>
<[email protected]><mailto:[email protected]>
Date: Tuesday, November 27, 2018 at 12:42 PM
To: "[email protected]"<mailto:[email protected]>
<[email protected]><mailto:[email protected]>
Subject: Re: build is broken : royale-asjs, mxroyale, sparkroyale
The latest version is not guaranteed to have publicly available
builds, so you have to build them yourself. It is to your advantage
to be able to build them yourself in order to pick up latest changes.
-Alex
From: Serkan Taş
<[email protected]><mailto:[email protected]>
Reply-To: "[email protected]"<mailto:[email protected]>
<[email protected]><mailto:[email protected]>
Date: Tuesday, November 27, 2018 at 12:38 PM
To: "[email protected]"<mailto:[email protected]>
<[email protected]><mailto:[email protected]>
Subject: Re: build is broken : royale-asjs, mxroyale, sparkroyale
No, royale-asjs also failed, but i did not build the other repositories.
I am going to follow your advises but, until now, i did not require
any other projects (royale-compiler, royale-typedefs) to build, just
mxroyale and sparkroyale sequentially maven build worked for me,
just for your attention.
Here are the builds i used :
MX
set MAVEN_OPTS=-Dfile.encoding=UTF-8 -Duser.country=EN -Duser.language=en
(cd
D:\dev\royale-emulation-works\github\royale-asjs\frameworks\projects\MXRoyale && mvn -DskipTests -Drat.skip=true clean
install)
SPARK
set MAVEN_OPTS=-Dfile.encoding=UTF-8 -Duser.country=EN -Duser.language=en
(cd
D:\dev\royale-emulation-works\github\royale-asjs\frameworks\projects\SparkRoyale && mvn -DskipTests -Drat.skip=true clean
install)
Thanks,
Serkan
27.11.2018 23:17 tarihinde Alex Harui yazdı:
Did the full build of royale-asjs succeed? MXRoyale will not build
until you have built all of its dependencies.
If you are using Maven, you will need to sync up all 3 repos
(royale-compiler, royale-typedefs-, royale-asjs).
In each repo in the order above, use “mvn clean install”.
-Alex
From: Serkan Taş
<[email protected]><mailto:[email protected]>
Reply-To: "[email protected]"<mailto:[email protected]>
<[email protected]><mailto:[email protected]>
Date: Tuesday, November 27, 2018 at 12:13 PM
To: "[email protected]"<mailto:[email protected]>
<[email protected]><mailto:[email protected]>
Subject: build is broken : royale-asjs, mxroyale, sparkroyale
Hi,
After version upgrade, i having build issues. MXRoyale, SparkRoyale
and royale-asjs maven build are all broken.
Here is the output for MXRoyale :
https://drive.google.com/open?id=1jfRezjjJTcVDCt84hkS19WVXGKB5eXX4<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1jfRezjjJTcVDCt84hkS19WVXGKB5eXX4&data=02%7C01%7Caharui%40adobe.com%7Cb0baba8c07ef48fc15bf08d654b018d4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636789512661379754&sdata=5QeOxiGg5%2FIMdFIYpw4DjbHg5v%2BanMGvoXMLvJlpyFo%3D&reserved=0>
Any help appreciated.
Thanks,
Serkan
--
Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
www.likyateknoloji.com
--------------------------------------
Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece
yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını
taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız
kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden
siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu
mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul
etmez.
This electronic mail and any files transmitted with it are intended
for the private use of the persons named above. If you received this
message in error, forwarding, copying or use of any of the information
is strictly prohibited. Please immediately notify the sender and
delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz.
Ltd. Şti. does not accept legal responsibility for the contents of
this message.
--------------------------------------
