First, to debug this you don't need to wait 40 minutes for the whole ant script
to run before it fails. You can simply specify the offending target like so:
ant -f ApproveRoyale.xml build_maven -Drelease.version=0.9.10
One thing you can try is to set vmlauncher [1] to false in line 810
<exec executable="${mvn}" vmlauncher="false"
dir="${basedir}/${maven.package.url.name}/royale-compiler" failonerror="true"
inputstring="Yes">
As I understand it, that should mimic you typing the command from the shell
which seems to be successful for you.
[1] Exec Task (apache.org)<https://ant.apache.org/manual/Tasks/exec.html>
________________________________
From: Maria Jose Esteve <mjest...@iest.com>
Sent: Tuesday, May 16, 2023 8:53 PM
To: dev@royale.apache.org <dev@royale.apache.org>
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4
Nothing, still with error [1]
- I have compiled with the call ant -v -e -f ApproveRoyale.xml
-Drelease.version=0.9.10 -Drc=4 instruction.
- I modified the ApproveRoyale.xml file in two ways:
* Putting blank space between the "-P" and the options.
* By adding the -e -X parameters to the Maven compilation instructions.
Which " ' " are you referring to?
[1]
Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-P option-with-swf'
'install'
'-e'
'-X'
The ' characters around the executable and arguments are
not part of the command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.
BUILD FAILED
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The
following error occurred while executing this line:
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec
returned: 1
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:675)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:699)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:527)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:106)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.Main.runBuild(Main.java:818)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
Total time: 38 minutes 41 seconds
D:\Develop_Royale\Projects\Royale-SDK\0.9.10
Hiedra
-----Mensaje original-----
De: Maria Jose Esteve <mjest...@iest.com>
Enviado el: martes, 16 de mayo de 2023 18:48
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4
No, this was not... (I removed the -v ☹ option, I try again).
Hiedra
-----Mensaje original-----
De: Maria Jose Esteve <mjest...@iest.com> Enviado el: martes, 16 de mayo de
2023 18:08
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4
I ran ant with -v, as suggested by Yishay, and it gave me the error detail:
Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-Poption-with-swf'
'install'
The ' characters around the executable and arguments are not part of
the command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.
I remember once I had this problem because a "blank space" was expected between
"P" and "option-with-swf"
I have included a blank space in all entries and relaunched the compilation [1].
[1]
https://drive.google.com/file/d/1FyboL0f4NnQswrfkEyk43TeFIpuPX9x9/view?usp=sharing
I have launched the compilation, I will come back here with the result.
Hiedra.
-----Mensaje original-----
De: Maria Jose Esteve <mjest...@iest.com> Enviado el: martes, 16 de mayo de
2023 14:06
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4
>Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can
>check by running where mvn in cmd).
Yes, I did, and everywhere I found it specified "mvn.cmd" and I have no
problem, it is with this script, and I don't know why.
> You can also set ant -v for verbose mode and see if that helps to diagnose
> the problem.
Ok, I'll give it a try and get back to you with the results.
Thx Yishay.
Hiedra
-----Mensaje original-----
De: Yishay Weiss <yishayj...@hotmail.com> Enviado el: martes, 16 de mayo de
2023 12:39
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can
check by running where mvn in cmd). If it's mvn then you can try to simply
remove lines 72-74 altogether. On my machine both mvn.cmd and mvn seem to work,
although it's a windows machine and supposedly mvn isn't guaranteed to work on
windows.
You can also set ant -v for verbose mode and see if that helps to diagnose the
problem.
________________________________
From: Maria Jose Esteve <mjest...@iest.com>
Sent: Tuesday, May 16, 2023 5:15 AM
To: dev@royale.apache.org <dev@royale.apache.org>
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4
I don't have mvn.exe in the /bin directory of Maven... but I tried it and it
didn't work.
I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml I modified
my build bat and manually set MAVEN_HOME, in case the system variable was
getting lost, but the result was the same.
The last test was to put MAVEN_HOME in first position in the path, also, same
error.
I have run out of ideas ☹
Hiedra
-----Mensaje original-----
De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: lunes, 15 de mayo de
2023 23:20
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
It seems to be failing when running Maven, but it's not giving you an error
message to explain what the issue is.
I see that you're on Windows. I wonder if you're having a similar issue that I
had on a previous release of the Royale build tools (I was on Windows at the
time, but I'm on macOS these days):
https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4
In this case, a similar workaround would be to change mvn.cmd to mvn.exe on
line 72 of ApproveRoyale.xml
<condition property="mvn" value="mvn.exe">
<isset property="isWindows" />
</condition>
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve <mjest...@iest.com> wrote:
> It has no longer included it as unapproved, but I still can't finish
> the Maven compilation, same problem but I don't know why, it's in the
> path. (I can compile the SDK normally with ant and with mvn and it
> hasn't given me any problems).
> any idea?
> ---------------------------------------------------------------
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R)
> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R)
> Management Engine Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:
> \Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\
> tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDat
> a\Roaming\npm;C:\Program
> Files\Microsoft Office\root\Client
>
> BUILD FAILED
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798:
> The following error occurred while executing this line:
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811:
> exec
> returned: 1
>
> Total time: 37 minutes 10 seconds
>
> ----------------------------------------------------------------------
> ------
>
> Hiedra
>
> -----Mensaje original-----
> De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: lunes, 15 de
> mayo de 2023 22:16
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> Yes, as I said, "You should be able to use it with this existing RC,
> if you'd like."
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve <mjest...@iest.com>
> wrote:
>
> > can I test this "ApproveRoyale.xml" with RC4 Josh?
> > Hiedra
> >
> > -----Mensaje original-----
> > De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: lunes, 15
> > de mayo de 2023 20:04
> > Para: dev@royale.apache.org
> > Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > That being said, I have updated the approval script in the
> > royale-asjs Git repo. You should be able to use it with this
> > existing RC, if you'd
> like.
> >
> > https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, May 15, 2023 at 9:35 AM Josh Tynjala
> > <joshtynj...@bowlerhat.dev>
> > wrote:
> >
> > > Now that I've had my morning tea, I remember now that I put
> > > RoyaleUnit's dependencies into a separate directory so that they
> > > don't conflict with anything else (and so that they aren't loaded
> > > by the compiler when they aren't needed). I didn't know that I
> > > needed to update ApproveRoyale.xml. I will get that fixed for
> > > *future*
> releases.
> > >
> > > For now, this is just a minor issue, and it should not prevent you
> > > from voting in favor of this RC. The license is actually allowed,
> > > but
> > "Rat"
> > > incorrectly flags it. The approval script will not fail when it
> > > mentions this license, so we don't need to do anything to fix it
> > > immediately.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Mon, May 15, 2023 at 8:55 AM Josh Tynjala
> > > <joshtynj...@bowlerhat.dev>
> > > wrote:
> > >
> > >> The approval script excludes dom4j-LICENSE.txt at the following
> > location:
> > >>
> > >> <exclude name="royale-asjs/js/lib/dom4j-LICENSE.txt"/>
> > >>
> > >> But your path is slightly different:
> > >>
> > >> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> > >>
> > >> I think we can just make a minor tweak to the approval script to
> > >> add this path too:
> > >>
> > >> <exclude name="royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt"/>
> > >>
> > >> --
> > >> Josh Tynjala
> > >> Bowler Hat LLC <https://bowlerhat.dev>
> > >>
> > >>
> > >> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve
> > >> <mjest...@iest.com>
> > >> wrote:
> > >>
> > >>> Hi,
> > >>> I keep testing the automated compilation option [1] the
> > >>> compilation gave me error ☹.
> > >>> I have left the log of the compilation here [2] but I attach the
> error:
> > >>>
> > >>> <<<<<<<
> > >>> ...
> > >>> main:
> > >>> Copying 1 file to
> > >>>
> > D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-sr
> > c\ royale-asjs\examples\native\USStatesMap\bin\js-debug
> > >>> Copying 1 file to
> > >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.1
> > >>> 0- sr c\royale-asjs\examples\native\USStatesMap\bin\js-release
> > >>>
> > >>> main:
> > >>>
> > >>> build_maven:
> > >>> Path is C:\Program Files (x86)\Common
> > >>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> > >>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\
> > >>> Ap
> > >>> ac
> > >>> he\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\cl
> > >>> ie
> > >>> nt
> > >>> _1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C
> > >>> :\
> > >>> Wi
> > >>> ndows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenS
> > >>> SH \; C:\Program Files (x86)\NVIDIA
> > >>> Corporation\PhysX\Common;C:\Program
> > >>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32
> > >>> \W
> > >>> be
> > >>> m;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System3
> > >>> 2\
> > >>> Op
> > >>> enSSH\;C:\Program
> > >>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> > >>> VS Code;C:\Program Files\Microsoft SQL Server\Client
> > >>> SDK\ODBC\170\Tools\Binn\;C:\Program
> > >>> Files\PowerShell\7-preview\preview;C:\Program Files
> > >>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit
> > >>> \n ek o;C:\Program Files\nodejs\;C:\Program Files
> > >>> (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program
> > >>> Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program
> > >>> Files (x86)\Pulse Secure\VC142.CRT\X64\;C:\Program Files
> > >>> (x86)\Pulse Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> > >>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> > >>> Server\130\Tools\Binn\;C:\Program Files
> > >>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsA
> > >>> pp
> > >>> s;
> > >>> C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\
> > >>> .d
> > >>> ot
> > >>> net\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:
> > >>> \U se rs\hiedra\AppData\Local\Programs\Microsoft
> > >>> VS
> > >>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\
> > >>> Ap
> > >>> pD
> > >>> ata\Roaming\npm
> > >>>
> > >>> BUILD FAILED
> > >>>
> > >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796:
> > >>> The following error occurred while executing this line:
> > >>>
> > >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809:
> > >>> exec
> > >>> returned: 1
> > >>>
> > >>> Total time: 39 minutes 52 seconds
> > >>> >>>>>>>
> > >>>
> > >>> The error occurs in the Maven compilation task (it's in the
> > >>> path, could it be because of the maven version?):
> > >>>
> > >>> >>>>>>>
> > >>> ...
> > >>> <target name="build_maven">
> > >>> <condition property="compiler_mvn_profiles"
> > >>> value="-Poption-with-swf"
> > >>> else="-Ddummy=true">
> > >>> <isset property="env.AIR_HOME" />
> > >>> </condition>
> > >>> <condition property="asjs_mvn_profiles"
> > >>> value="-Pwith-examples,with-distribution,option-with-swf"
> > >>> else="-Pwith-examples,with-distribution">
> > >>> <isset property="env.AIR_HOME" />
> > >>> </condition>
> > >>> <echo>Path is ${env.Path}</echo>
> > >>>
> > >>> -- >>> <exec executable="${mvn}" dir="${basedir}/${
> > >>> maven.package.url.name}/royale-compiler" failonerror="true"
> > >>> inputstring="Yes">
> > >>> <arg value="clean" />
> > >>> <arg value="${compiler_mvn_profiles}" />
> > >>> <arg value="install" />
> > >>> </exec>
> > >>> <exec executable="${mvn}" dir="${basedir}/${
> > >>> maven.package.url.name}/royale-typedefs" failonerror="true" >
> > >>> <arg value="clean" />
> > >>> <arg value="install" />
> > >>> </exec>
> > >>> <exec executable="${mvn}" dir="${basedir}/${
> > >>> maven.package.url.name}/royale-asjs" failonerror="true"
> > >>> inputstring="Yes">
> > >>> <arg value="clean" />
> > >>> <arg value="${asjs_mvn_profiles}" />
> > >>> <arg value="install" />
> > >>> </exec>
> > >>> </target>
> > >>> ...
> > >>> <<<<<<<
> > >>>
> > >>> I have a question about licenses... Yishay has no anomalies in
> > >>> this regard but I have an unapproved license:
> > >>> Unapproved licenses:
> > >>>
> > >>>
> > >>> D:/Develop_Royale/Projects/Royale-SDK/0.9.10/apache-royale-0.9.1
> > >>> 0- bi n-js-swf/royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> > >>> How can I fix it?
> > >>>
> > >>> [1]
> > >>> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/Approve
> > >>> Ro
> > >>> ya
> > >>> le.xml
> > >>> y ejecutando el script:
> > >>> ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
> > >>> [2]
> > >>> https://drive.google.com/file/d/1jCgS51cgtRSSuh11UJUxzdEaburpDdp
> > >>> F/
> > >>> vi
> > >>> ew?usp=share_link
> > >>>
> > >>> Hiedra
> > >>>
> > >>> -----Mensaje original-----
> > >>> De: Yishay Weiss <yishayj...@hotmail.com> Enviado el: sábado, 13
> > >>> de mayo de 2023 19:36
> > >>> Para: dev@royale.apache.org
> > >>> Asunto: [DISCUSS] Release Apache Royale 0.9.10 RC4
> > >>>
> > >>> This is the discussion thread.
> > >>>
> > >>
> >
>
