You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Piotr Zarzycki <pi...@gmail.com> on 2020/01/22 09:19:04 UTC
Building Royale project with Maven throws NPE
Hi Guys,
I have just tired build our project with Maven (we are using it when wanted
to deploy version on the server) and I'm getting following compilation
error:
got null for string/internal.js
> got null for debug/errorcontext.js
> got null for debug/debug.js
> Internal error: java.lang.NullPointerException
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Anyone know what it could be ? I don't have such errors when I'm building
stuff using Moonshine. - I have used in that case following version of
Nightly [1]
[1]
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
Thanks,
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Testing distribution is being handled in separate thread - you are mixing
subjects :)
śr., 22 sty 2020 o 13:22 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Exactly we are not discussion any stuff related to distribution :) We are
> discussion at some point that maybe for some reason your changes influence
> somehow compiler or anything else which end up with above error. Maybe that
> closure upgrade - I don't know. I look forward to hear more from someone
> what could know the reason of my issue.
>
> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Hi Piotr,
>>
>> El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
>> piotrzarzycki21@gmail.com>) escribió:
>>
>> >
>> >
>> > Nope. Let's pretend that you have clean PC. You have downloaded your
>> Royale
>> > application which contains pom.xml - You do "mvn clean install" - All
>> the
>> > dependencies will be downloaded from Apache Maven Central repository -
>> > which is being updated by every build ->
>> > https://builds.apache.org/job/Royale-asjs/ - Do you understand now what
>> > I'm
>> > using now ?
>> >
>> >
>> Ok, but in that case, you are not trying "distribution".... so really
>> don't
>> understand.
>> I though we were discussing the new fixed distribution that creates a SDK
>> in target folder or in the folder you specify (if use
>> -DdistributionTargetFolder var)
>> IOW, ant and maven continue to do the same as before, since there's no
>> changes out side of distribution (just class paths set ups for maven
>> generated artifacts that until now was empty or pointing to not existing
>> resources)
>>
>>
>> > No I don't have to and I shouldn't have to - I'm using artifacts from
>> > Apache Maven Central.
>> >
>> >
>> In that case you're not testing distribution. Jenkins builds the same as
>> always. Other case will be if we can change Jenkins to build with
>> distribution and then provide that SDK to download, that will be the
>> proper
>> way, and what the rest of projects using maven does in fact.
>>
>>
>>
>>
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>> >
>> >
>> >
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: InvalidPathException: Illegal char (was: Building Royale project
with Maven throws NPE)
Posted by Piotr Zarzycki <pi...@gmail.com>.
Great to know! Thanks!
czw., 23 sty 2020 o 18:41 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> IIRC, you only get the "has been successfully compiled" message if
> -debug=false. That message comes from Closure Compiler.
>
> -Alex
>
> On 1/23/20, 8:54 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> I do have other project which is using PureMVC - I could compare with
> that.
> Anyway it is problem with source-map, cause when I do -source-map=false
> above problem gone.
>
> However everything looks like my project didn't fully finished
> building,
> cause at the end of the build compiler is sending:
>
> : The project 'NameOfTheProject' has been successfully compiled.
>
> I don't get that message - What could be the reason ? Files are
> generated
> in bin.
>
> Thanks,
> Piotr
>
>
> śr., 22 sty 2020 o 19:35 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > Is the URL for Notifier.as valid?
> >
> > Do you have an older project around that you can compare the source
> > mapping URLs? Looks like Google is complaining about the source map
> URL.
> >
> > -Alex
> >
> > On 1/22/20, 9:01 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > It looks like I have two separate issues - apart of behavior
> when I'm
> > building application by Maven - I'm getting this using Moonshine.
> >
> > In the morning this error points to different class. Now when I
> > downloaded
> > newest Nightly build - it points to some PureMVC class.
> >
> > : Internal error: java.nio.file.InvalidPathException: Illegal
> char <:>
> > at
> > index 4:
> >
> >
> file:///D:/Work/projects/Prominic.NET/ProminicNative/repository/puremvc-as3-multicore-framework/src/org/puremvc/as3/multicore/patterns/observer/Notifier.as
> >
> >
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.SourceMap.addMapping(SourceMap.java:177)com.google.javascript.jscomp.CodePrinter$MappedCodePrinter.generateSourceMap(CodePrinter.java:141)com.google.javascript.jscomp.CodePrinter.toSource(CodePrinter.java:911)com.google.javascript.jscomp.CodePrinter.access$300(CodePrinter.java:42)com.google.javascript.jscomp.CodePrinter$Builder.build(CodePrinter.java:840)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2295)com.google.javascript.jscomp.Compiler.lambda$toSource$9(Compiler.java:2256)com.google.javascript.jscomp.Compiler$$Lambda$96.000000001354F550.call(Unknown
> >
> >
> Source)com.google.javascript.jscomp.CompilerExecutor.runInCompilerThread(CompilerExecutor.java:129)com.google.javascript.jscomp.Compiler.runInCompilerThread(Compiler.java:876)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2218)com.google.javascript.jscomp.Compiler.lambda$toSource$7(Compiler.java:2175)com.google.javascript.jscomp.Compiler$$Lambda$95.0000000011211140.call(Unknown
> >
> >
> Source)com.google.javascript.jscomp.CompilerExecutor$2.call(CompilerExecutor.java:102)java.util.concurrent.FutureTask.run(FutureTask.java:266)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)java.lang.Thread.run(Thread.java:813)
> >
> >
> > Thanks,
> > Piotr
> >
> > śr., 22 sty 2020 o 16:05 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > napisał(a):
> >
> > > Build is in progress. Once it's finish I will check ->
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-compiler%2F1257%2F&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=teV6A2erCvEPdyMrY%2FufEiOYRIwbFS97izetCZUz2N0%3D&reserved=0
> > >
> > > śr., 22 sty 2020 o 15:54 Carlos Rovira <
> carlosrovira@apache.org>
> > > napisał(a):
> > >
> > >> Hi Piotr,
> > >> latest commit seems to fix the problem. Let me know if all is
> now ok
> > >> sorry for the inconvenience
> > >> Carlos
> > >>
> > >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> > >> carlosrovira@apache.org>)
> > >> escribió:
> > >>
> > >> > Hi Piotr,
> > >> >
> > >> > I can see the problem is related to my latest commit in
> compiler
> > to
> > >> solve
> > >> > the GOOG_HOME problem.
> > >> > going to fix it
> > >> >
> > >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> > >> carlosrovira@apache.org>)
> > >> > escribió:
> > >> >
> > >> >> Hi Piotr,
> > >> >>
> > >> >> ok, now I understand... It's clear that I broke something
> since
> > trying
> > >> to
> > >> >> build now with Maven is generating the same issue ;)
> > >> >> I was focused on making build works for IDEs, that didn't
> test
> > normal
> > >> >> maven path yesterday.
> > >> >> I'll be looking over it to find where is the problem
> > >> >> Sorry for the confusion! :)
> > >> >>
> > >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> > >> >> carlosrovira@apache.org>) escribió:
> > >> >>
> > >> >>> Hi Piotr,
> > >> >>>
> > >> >>> before understand the mistake, I downloaded and tested
> SDK from
> > >> Jenkins
> > >> >>> (build #2552 that was the latest created) and build TDJ
> with
> > VSCode
> > >> and all
> > >> >>> worked ok (the same output as with Maven distribution
> created
> > locally)
> > >> >>> Don't know if that report can be of help for you.
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> > >> >>> piotrzarzycki21@gmail.com>) escribió:
> > >> >>>
> > >> >>>> Exactly we are not discussion any stuff related to
> > distribution :) We
> > >> >>>> are
> > >> >>>> discussion at some point that maybe for some reason your
> > changes
> > >> >>>> influence
> > >> >>>> somehow compiler or anything else which end up with above
> > error.
> > >> Maybe
> > >> >>>> that
> > >> >>>> closure upgrade - I don't know. I look forward to hear
> more
> > from
> > >> someone
> > >> >>>> what could know the reason of my issue.
> > >> >>>>
> > >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <
> > carlosrovira@apache.org>
> > >> >>>> napisał(a):
> > >> >>>>
> > >> >>>> > Hi Piotr,
> > >> >>>> >
> > >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> > >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> > >> >>>> >
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > > Nope. Let's pretend that you have clean PC. You have
> > downloaded
> > >> your
> > >> >>>> > Royale
> > >> >>>> > > application which contains pom.xml - You do "mvn
> clean
> > install" -
> > >> >>>> All the
> > >> >>>> > > dependencies will be downloaded from Apache Maven
> Central
> > >> >>>> repository -
> > >> >>>> > > which is being updated by every build ->
> > >> >>>> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-asjs%2F&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=HDfeqeGNS3qC2rweNHQF4ODkI0YIDtnK2xxlUlajbwo%3D&reserved=0
> > - Do you understand
> > >> now
> > >> >>>> what
> > >> >>>> > > I'm
> > >> >>>> > > using now ?
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > Ok, but in that case, you are not trying
> "distribution"....
> > so
> > >> really
> > >> >>>> don't
> > >> >>>> > understand.
> > >> >>>> > I though we were discussing the new fixed distribution
> that
> > >> creates a
> > >> >>>> SDK
> > >> >>>> > in target folder or in the folder you specify (if use
> > >> >>>> > -DdistributionTargetFolder var)
> > >> >>>> > IOW, ant and maven continue to do the same as before,
> since
> > >> there's no
> > >> >>>> > changes out side of distribution (just class paths set
> ups
> > for
> > >> maven
> > >> >>>> > generated artifacts that until now was empty or
> pointing to
> > not
> > >> >>>> existing
> > >> >>>> > resources)
> > >> >>>> >
> > >> >>>> >
> > >> >>>> > > No I don't have to and I shouldn't have to - I'm
> using
> > artifacts
> > >> >>>> from
> > >> >>>> > > Apache Maven Central.
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > In that case you're not testing distribution. Jenkins
> builds
> > the
> > >> same
> > >> >>>> as
> > >> >>>> > always. Other case will be if we can change Jenkins to
> build
> > with
> > >> >>>> > distribution and then provide that SDK to download,
> that
> > will be
> > >> the
> > >> >>>> proper
> > >> >>>> > way, and what the rest of projects using maven does in
> fact.
> > >> >>>> >
> > >> >>>> >
> > >> >>>> >
> > >> >>>> >
> > >> >>>> > > --
> > >> >>>> > > Carlos Rovira
> > >> >>>> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> >
> > >> >>>>
> > >> >>>>
> > >> >>>> --
> > >> >>>>
> > >> >>>> Piotr Zarzycki
> > >> >>>>
> > >> >>>> Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=53SrAQ1P5qbNipeo8BFaxfLsTvbSIYvab2EJnKAKZk4%3D&reserved=0
> > >> >>>> <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=53SrAQ1P5qbNipeo8BFaxfLsTvbSIYvab2EJnKAKZk4%3D&reserved=0
> > >*
> > >> >>>>
> > >> >>>
> > >> >>>
> > >> >>> --
> > >> >>> Carlos Rovira
> > >> >>>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>
> > >> >> --
> > >> >> Carlos Rovira
> > >> >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> > >> >>
> > >> >>
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> > >> >
> > >> >
> > >>
> > >> --
> > >> Carlos Rovira
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> > >*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: InvalidPathException: Illegal char (was: Building Royale project
with Maven throws NPE)
Posted by Alex Harui <ah...@adobe.com.INVALID>.
IIRC, you only get the "has been successfully compiled" message if -debug=false. That message comes from Closure Compiler.
-Alex
On 1/23/20, 8:54 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
I do have other project which is using PureMVC - I could compare with that.
Anyway it is problem with source-map, cause when I do -source-map=false
above problem gone.
However everything looks like my project didn't fully finished building,
cause at the end of the build compiler is sending:
: The project 'NameOfTheProject' has been successfully compiled.
I don't get that message - What could be the reason ? Files are generated
in bin.
Thanks,
Piotr
śr., 22 sty 2020 o 19:35 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> Is the URL for Notifier.as valid?
>
> Do you have an older project around that you can compare the source
> mapping URLs? Looks like Google is complaining about the source map URL.
>
> -Alex
>
> On 1/22/20, 9:01 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> It looks like I have two separate issues - apart of behavior when I'm
> building application by Maven - I'm getting this using Moonshine.
>
> In the morning this error points to different class. Now when I
> downloaded
> newest Nightly build - it points to some PureMVC class.
>
> : Internal error: java.nio.file.InvalidPathException: Illegal char <:>
> at
> index 4:
>
> file:///D:/Work/projects/Prominic.NET/ProminicNative/repository/puremvc-as3-multicore-framework/src/org/puremvc/as3/multicore/patterns/observer/Notifier.as
>
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.SourceMap.addMapping(SourceMap.java:177)com.google.javascript.jscomp.CodePrinter$MappedCodePrinter.generateSourceMap(CodePrinter.java:141)com.google.javascript.jscomp.CodePrinter.toSource(CodePrinter.java:911)com.google.javascript.jscomp.CodePrinter.access$300(CodePrinter.java:42)com.google.javascript.jscomp.CodePrinter$Builder.build(CodePrinter.java:840)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2295)com.google.javascript.jscomp.Compiler.lambda$toSource$9(Compiler.java:2256)com.google.javascript.jscomp.Compiler$$Lambda$96.000000001354F550.call(Unknown
>
> Source)com.google.javascript.jscomp.CompilerExecutor.runInCompilerThread(CompilerExecutor.java:129)com.google.javascript.jscomp.Compiler.runInCompilerThread(Compiler.java:876)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2218)com.google.javascript.jscomp.Compiler.lambda$toSource$7(Compiler.java:2175)com.google.javascript.jscomp.Compiler$$Lambda$95.0000000011211140.call(Unknown
>
> Source)com.google.javascript.jscomp.CompilerExecutor$2.call(CompilerExecutor.java:102)java.util.concurrent.FutureTask.run(FutureTask.java:266)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)java.lang.Thread.run(Thread.java:813)
>
>
> Thanks,
> Piotr
>
> śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Build is in progress. Once it's finish I will check ->
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-compiler%2F1257%2F&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=teV6A2erCvEPdyMrY%2FufEiOYRIwbFS97izetCZUz2N0%3D&reserved=0
> >
> > śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> Hi Piotr,
> >> latest commit seems to fix the problem. Let me know if all is now ok
> >> sorry for the inconvenience
> >> Carlos
> >>
> >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >> escribió:
> >>
> >> > Hi Piotr,
> >> >
> >> > I can see the problem is related to my latest commit in compiler
> to
> >> solve
> >> > the GOOG_HOME problem.
> >> > going to fix it
> >> >
> >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >> > escribió:
> >> >
> >> >> Hi Piotr,
> >> >>
> >> >> ok, now I understand... It's clear that I broke something since
> trying
> >> to
> >> >> build now with Maven is generating the same issue ;)
> >> >> I was focused on making build works for IDEs, that didn't test
> normal
> >> >> maven path yesterday.
> >> >> I'll be looking over it to find where is the problem
> >> >> Sorry for the confusion! :)
> >> >>
> >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> >> >> carlosrovira@apache.org>) escribió:
> >> >>
> >> >>> Hi Piotr,
> >> >>>
> >> >>> before understand the mistake, I downloaded and tested SDK from
> >> Jenkins
> >> >>> (build #2552 that was the latest created) and build TDJ with
> VSCode
> >> and all
> >> >>> worked ok (the same output as with Maven distribution created
> locally)
> >> >>> Don't know if that report can be of help for you.
> >> >>>
> >> >>>
> >> >>>
> >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> >> >>> piotrzarzycki21@gmail.com>) escribió:
> >> >>>
> >> >>>> Exactly we are not discussion any stuff related to
> distribution :) We
> >> >>>> are
> >> >>>> discussion at some point that maybe for some reason your
> changes
> >> >>>> influence
> >> >>>> somehow compiler or anything else which end up with above
> error.
> >> Maybe
> >> >>>> that
> >> >>>> closure upgrade - I don't know. I look forward to hear more
> from
> >> someone
> >> >>>> what could know the reason of my issue.
> >> >>>>
> >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <
> carlosrovira@apache.org>
> >> >>>> napisał(a):
> >> >>>>
> >> >>>> > Hi Piotr,
> >> >>>> >
> >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> >> >>>> >
> >> >>>> > >
> >> >>>> > >
> >> >>>> > > Nope. Let's pretend that you have clean PC. You have
> downloaded
> >> your
> >> >>>> > Royale
> >> >>>> > > application which contains pom.xml - You do "mvn clean
> install" -
> >> >>>> All the
> >> >>>> > > dependencies will be downloaded from Apache Maven Central
> >> >>>> repository -
> >> >>>> > > which is being updated by every build ->
> >> >>>> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-asjs%2F&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=HDfeqeGNS3qC2rweNHQF4ODkI0YIDtnK2xxlUlajbwo%3D&reserved=0
> - Do you understand
> >> now
> >> >>>> what
> >> >>>> > > I'm
> >> >>>> > > using now ?
> >> >>>> > >
> >> >>>> > >
> >> >>>> > Ok, but in that case, you are not trying "distribution"....
> so
> >> really
> >> >>>> don't
> >> >>>> > understand.
> >> >>>> > I though we were discussing the new fixed distribution that
> >> creates a
> >> >>>> SDK
> >> >>>> > in target folder or in the folder you specify (if use
> >> >>>> > -DdistributionTargetFolder var)
> >> >>>> > IOW, ant and maven continue to do the same as before, since
> >> there's no
> >> >>>> > changes out side of distribution (just class paths set ups
> for
> >> maven
> >> >>>> > generated artifacts that until now was empty or pointing to
> not
> >> >>>> existing
> >> >>>> > resources)
> >> >>>> >
> >> >>>> >
> >> >>>> > > No I don't have to and I shouldn't have to - I'm using
> artifacts
> >> >>>> from
> >> >>>> > > Apache Maven Central.
> >> >>>> > >
> >> >>>> > >
> >> >>>> > In that case you're not testing distribution. Jenkins builds
> the
> >> same
> >> >>>> as
> >> >>>> > always. Other case will be if we can change Jenkins to build
> with
> >> >>>> > distribution and then provide that SDK to download, that
> will be
> >> the
> >> >>>> proper
> >> >>>> > way, and what the rest of projects using maven does in fact.
> >> >>>> >
> >> >>>> >
> >> >>>> >
> >> >>>> >
> >> >>>> > > --
> >> >>>> > > Carlos Rovira
> >> >>>> > >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> >> >>>> > >
> >> >>>> > >
> >> >>>> > >
> >> >>>> > >
> >> >>>> >
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>>
> >> >>>> Piotr Zarzycki
> >> >>>>
> >> >>>> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=53SrAQ1P5qbNipeo8BFaxfLsTvbSIYvab2EJnKAKZk4%3D&reserved=0
> >> >>>> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=53SrAQ1P5qbNipeo8BFaxfLsTvbSIYvab2EJnKAKZk4%3D&reserved=0
> >*
> >> >>>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Carlos Rovira
> >> >>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> >> >>>
> >> >>>
> >> >>
> >> >> --
> >> >> Carlos Rovira
> >> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> >> >>
> >> >>
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> >> >
> >> >
> >>
> >> --
> >> Carlos Rovira
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436151201&sdata=oNue2zv4ivDdCOh9iuCK7m5EuMiXaIbpoeM0TRDQaJE%3D&reserved=0
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C8ae18483c04c44eb726f08d7a024d8f4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153952436161192&sdata=ea2p2GzZnuL9RvGRTWItCRZXkwlYqCjz%2FU4DShwVCYs%3D&reserved=0>*
Re: InvalidPathException: Illegal char (was: Building Royale project
with Maven throws NPE)
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
I do have other project which is using PureMVC - I could compare with that.
Anyway it is problem with source-map, cause when I do -source-map=false
above problem gone.
However everything looks like my project didn't fully finished building,
cause at the end of the build compiler is sending:
: The project 'NameOfTheProject' has been successfully compiled.
I don't get that message - What could be the reason ? Files are generated
in bin.
Thanks,
Piotr
śr., 22 sty 2020 o 19:35 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> Is the URL for Notifier.as valid?
>
> Do you have an older project around that you can compare the source
> mapping URLs? Looks like Google is complaining about the source map URL.
>
> -Alex
>
> On 1/22/20, 9:01 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> It looks like I have two separate issues - apart of behavior when I'm
> building application by Maven - I'm getting this using Moonshine.
>
> In the morning this error points to different class. Now when I
> downloaded
> newest Nightly build - it points to some PureMVC class.
>
> : Internal error: java.nio.file.InvalidPathException: Illegal char <:>
> at
> index 4:
>
> file:///D:/Work/projects/Prominic.NET/ProminicNative/repository/puremvc-as3-multicore-framework/src/org/puremvc/as3/multicore/patterns/observer/Notifier.as
>
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.SourceMap.addMapping(SourceMap.java:177)com.google.javascript.jscomp.CodePrinter$MappedCodePrinter.generateSourceMap(CodePrinter.java:141)com.google.javascript.jscomp.CodePrinter.toSource(CodePrinter.java:911)com.google.javascript.jscomp.CodePrinter.access$300(CodePrinter.java:42)com.google.javascript.jscomp.CodePrinter$Builder.build(CodePrinter.java:840)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2295)com.google.javascript.jscomp.Compiler.lambda$toSource$9(Compiler.java:2256)com.google.javascript.jscomp.Compiler$$Lambda$96.000000001354F550.call(Unknown
>
> Source)com.google.javascript.jscomp.CompilerExecutor.runInCompilerThread(CompilerExecutor.java:129)com.google.javascript.jscomp.Compiler.runInCompilerThread(Compiler.java:876)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2218)com.google.javascript.jscomp.Compiler.lambda$toSource$7(Compiler.java:2175)com.google.javascript.jscomp.Compiler$$Lambda$95.0000000011211140.call(Unknown
>
> Source)com.google.javascript.jscomp.CompilerExecutor$2.call(CompilerExecutor.java:102)java.util.concurrent.FutureTask.run(FutureTask.java:266)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)java.lang.Thread.run(Thread.java:813)
>
>
> Thanks,
> Piotr
>
> śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Build is in progress. Once it's finish I will check ->
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-compiler%2F1257%2F&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=%2BCAga9hDYjBZoU5yhKxxJ8WpYQXGWsTVKNgy49FHMmM%3D&reserved=0
> >
> > śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> Hi Piotr,
> >> latest commit seems to fix the problem. Let me know if all is now ok
> >> sorry for the inconvenience
> >> Carlos
> >>
> >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >> escribió:
> >>
> >> > Hi Piotr,
> >> >
> >> > I can see the problem is related to my latest commit in compiler
> to
> >> solve
> >> > the GOOG_HOME problem.
> >> > going to fix it
> >> >
> >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >> > escribió:
> >> >
> >> >> Hi Piotr,
> >> >>
> >> >> ok, now I understand... It's clear that I broke something since
> trying
> >> to
> >> >> build now with Maven is generating the same issue ;)
> >> >> I was focused on making build works for IDEs, that didn't test
> normal
> >> >> maven path yesterday.
> >> >> I'll be looking over it to find where is the problem
> >> >> Sorry for the confusion! :)
> >> >>
> >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> >> >> carlosrovira@apache.org>) escribió:
> >> >>
> >> >>> Hi Piotr,
> >> >>>
> >> >>> before understand the mistake, I downloaded and tested SDK from
> >> Jenkins
> >> >>> (build #2552 that was the latest created) and build TDJ with
> VSCode
> >> and all
> >> >>> worked ok (the same output as with Maven distribution created
> locally)
> >> >>> Don't know if that report can be of help for you.
> >> >>>
> >> >>>
> >> >>>
> >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> >> >>> piotrzarzycki21@gmail.com>) escribió:
> >> >>>
> >> >>>> Exactly we are not discussion any stuff related to
> distribution :) We
> >> >>>> are
> >> >>>> discussion at some point that maybe for some reason your
> changes
> >> >>>> influence
> >> >>>> somehow compiler or anything else which end up with above
> error.
> >> Maybe
> >> >>>> that
> >> >>>> closure upgrade - I don't know. I look forward to hear more
> from
> >> someone
> >> >>>> what could know the reason of my issue.
> >> >>>>
> >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <
> carlosrovira@apache.org>
> >> >>>> napisał(a):
> >> >>>>
> >> >>>> > Hi Piotr,
> >> >>>> >
> >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> >> >>>> >
> >> >>>> > >
> >> >>>> > >
> >> >>>> > > Nope. Let's pretend that you have clean PC. You have
> downloaded
> >> your
> >> >>>> > Royale
> >> >>>> > > application which contains pom.xml - You do "mvn clean
> install" -
> >> >>>> All the
> >> >>>> > > dependencies will be downloaded from Apache Maven Central
> >> >>>> repository -
> >> >>>> > > which is being updated by every build ->
> >> >>>> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-asjs%2F&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=V%2B7NQq0ajNfCfPWhJZ0v8Zik7TdcKQf%2BzZy%2FnhfqzWM%3D&reserved=0
> - Do you understand
> >> now
> >> >>>> what
> >> >>>> > > I'm
> >> >>>> > > using now ?
> >> >>>> > >
> >> >>>> > >
> >> >>>> > Ok, but in that case, you are not trying "distribution"....
> so
> >> really
> >> >>>> don't
> >> >>>> > understand.
> >> >>>> > I though we were discussing the new fixed distribution that
> >> creates a
> >> >>>> SDK
> >> >>>> > in target folder or in the folder you specify (if use
> >> >>>> > -DdistributionTargetFolder var)
> >> >>>> > IOW, ant and maven continue to do the same as before, since
> >> there's no
> >> >>>> > changes out side of distribution (just class paths set ups
> for
> >> maven
> >> >>>> > generated artifacts that until now was empty or pointing to
> not
> >> >>>> existing
> >> >>>> > resources)
> >> >>>> >
> >> >>>> >
> >> >>>> > > No I don't have to and I shouldn't have to - I'm using
> artifacts
> >> >>>> from
> >> >>>> > > Apache Maven Central.
> >> >>>> > >
> >> >>>> > >
> >> >>>> > In that case you're not testing distribution. Jenkins builds
> the
> >> same
> >> >>>> as
> >> >>>> > always. Other case will be if we can change Jenkins to build
> with
> >> >>>> > distribution and then provide that SDK to download, that
> will be
> >> the
> >> >>>> proper
> >> >>>> > way, and what the rest of projects using maven does in fact.
> >> >>>> >
> >> >>>> >
> >> >>>> >
> >> >>>> >
> >> >>>> > > --
> >> >>>> > > Carlos Rovira
> >> >>>> > >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
> >> >>>> > >
> >> >>>> > >
> >> >>>> > >
> >> >>>> > >
> >> >>>> >
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>>
> >> >>>> Piotr Zarzycki
> >> >>>>
> >> >>>> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
> >> >>>> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
> >*
> >> >>>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Carlos Rovira
> >> >>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
> >> >>>
> >> >>>
> >> >>
> >> >> --
> >> >> Carlos Rovira
> >> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
> >> >>
> >> >>
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
> >> >
> >> >
> >>
> >> --
> >> Carlos Rovira
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: InvalidPathException: Illegal char (was: Building Royale project
with Maven throws NPE)
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Is the URL for Notifier.as valid?
Do you have an older project around that you can compare the source mapping URLs? Looks like Google is complaining about the source map URL.
-Alex
On 1/22/20, 9:01 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
It looks like I have two separate issues - apart of behavior when I'm
building application by Maven - I'm getting this using Moonshine.
In the morning this error points to different class. Now when I downloaded
newest Nightly build - it points to some PureMVC class.
: Internal error: java.nio.file.InvalidPathException: Illegal char <:> at
index 4:
file:///D:/Work/projects/Prominic.NET/ProminicNative/repository/puremvc-as3-multicore-framework/src/org/puremvc/as3/multicore/patterns/observer/Notifier.as
sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.SourceMap.addMapping(SourceMap.java:177)com.google.javascript.jscomp.CodePrinter$MappedCodePrinter.generateSourceMap(CodePrinter.java:141)com.google.javascript.jscomp.CodePrinter.toSource(CodePrinter.java:911)com.google.javascript.jscomp.CodePrinter.access$300(CodePrinter.java:42)com.google.javascript.jscomp.CodePrinter$Builder.build(CodePrinter.java:840)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2295)com.google.javascript.jscomp.Compiler.lambda$toSource$9(Compiler.java:2256)com.google.javascript.jscomp.Compiler$$Lambda$96.000000001354F550.call(Unknown
Source)com.google.javascript.jscomp.CompilerExecutor.runInCompilerThread(CompilerExecutor.java:129)com.google.javascript.jscomp.Compiler.runInCompilerThread(Compiler.java:876)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2218)com.google.javascript.jscomp.Compiler.lambda$toSource$7(Compiler.java:2175)com.google.javascript.jscomp.Compiler$$Lambda$95.0000000011211140.call(Unknown
Source)com.google.javascript.jscomp.CompilerExecutor$2.call(CompilerExecutor.java:102)java.util.concurrent.FutureTask.run(FutureTask.java:266)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)java.lang.Thread.run(Thread.java:813)
Thanks,
Piotr
śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Build is in progress. Once it's finish I will check ->
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-compiler%2F1257%2F&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=%2BCAga9hDYjBZoU5yhKxxJ8WpYQXGWsTVKNgy49FHMmM%3D&reserved=0
>
> śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Hi Piotr,
>> latest commit seems to fix the problem. Let me know if all is now ok
>> sorry for the inconvenience
>> Carlos
>>
>> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
>> carlosrovira@apache.org>)
>> escribió:
>>
>> > Hi Piotr,
>> >
>> > I can see the problem is related to my latest commit in compiler to
>> solve
>> > the GOOG_HOME problem.
>> > going to fix it
>> >
>> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
>> carlosrovira@apache.org>)
>> > escribió:
>> >
>> >> Hi Piotr,
>> >>
>> >> ok, now I understand... It's clear that I broke something since trying
>> to
>> >> build now with Maven is generating the same issue ;)
>> >> I was focused on making build works for IDEs, that didn't test normal
>> >> maven path yesterday.
>> >> I'll be looking over it to find where is the problem
>> >> Sorry for the confusion! :)
>> >>
>> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
>> >> carlosrovira@apache.org>) escribió:
>> >>
>> >>> Hi Piotr,
>> >>>
>> >>> before understand the mistake, I downloaded and tested SDK from
>> Jenkins
>> >>> (build #2552 that was the latest created) and build TDJ with VSCode
>> and all
>> >>> worked ok (the same output as with Maven distribution created locally)
>> >>> Don't know if that report can be of help for you.
>> >>>
>> >>>
>> >>>
>> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
>> >>> piotrzarzycki21@gmail.com>) escribió:
>> >>>
>> >>>> Exactly we are not discussion any stuff related to distribution :) We
>> >>>> are
>> >>>> discussion at some point that maybe for some reason your changes
>> >>>> influence
>> >>>> somehow compiler or anything else which end up with above error.
>> Maybe
>> >>>> that
>> >>>> closure upgrade - I don't know. I look forward to hear more from
>> someone
>> >>>> what could know the reason of my issue.
>> >>>>
>> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
>> >>>> napisał(a):
>> >>>>
>> >>>> > Hi Piotr,
>> >>>> >
>> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
>> >>>> > piotrzarzycki21@gmail.com>) escribió:
>> >>>> >
>> >>>> > >
>> >>>> > >
>> >>>> > > Nope. Let's pretend that you have clean PC. You have downloaded
>> your
>> >>>> > Royale
>> >>>> > > application which contains pom.xml - You do "mvn clean install" -
>> >>>> All the
>> >>>> > > dependencies will be downloaded from Apache Maven Central
>> >>>> repository -
>> >>>> > > which is being updated by every build ->
>> >>>> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-asjs%2F&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=V%2B7NQq0ajNfCfPWhJZ0v8Zik7TdcKQf%2BzZy%2FnhfqzWM%3D&reserved=0 - Do you understand
>> now
>> >>>> what
>> >>>> > > I'm
>> >>>> > > using now ?
>> >>>> > >
>> >>>> > >
>> >>>> > Ok, but in that case, you are not trying "distribution".... so
>> really
>> >>>> don't
>> >>>> > understand.
>> >>>> > I though we were discussing the new fixed distribution that
>> creates a
>> >>>> SDK
>> >>>> > in target folder or in the folder you specify (if use
>> >>>> > -DdistributionTargetFolder var)
>> >>>> > IOW, ant and maven continue to do the same as before, since
>> there's no
>> >>>> > changes out side of distribution (just class paths set ups for
>> maven
>> >>>> > generated artifacts that until now was empty or pointing to not
>> >>>> existing
>> >>>> > resources)
>> >>>> >
>> >>>> >
>> >>>> > > No I don't have to and I shouldn't have to - I'm using artifacts
>> >>>> from
>> >>>> > > Apache Maven Central.
>> >>>> > >
>> >>>> > >
>> >>>> > In that case you're not testing distribution. Jenkins builds the
>> same
>> >>>> as
>> >>>> > always. Other case will be if we can change Jenkins to build with
>> >>>> > distribution and then provide that SDK to download, that will be
>> the
>> >>>> proper
>> >>>> > way, and what the rest of projects using maven does in fact.
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > > --
>> >>>> > > Carlos Rovira
>> >>>> > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> >
>> >>>>
>> >>>>
>> >>>> --
>> >>>>
>> >>>> Piotr Zarzycki
>> >>>>
>> >>>> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
>> >>>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0>*
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
>> >>>
>> >>>
>> >>
>> >> --
>> >> Carlos Rovira
>> >> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
>> >>
>> >>
>> >
>> > --
>> > Carlos Rovira
>> > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
>> >
>> >
>>
>> --
>> Carlos Rovira
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=K0DETyXu4f3Jkh7tObQcyehs%2FO23SiJ8Uny8YIFg%2Bt8%3D&reserved=0
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0>*
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc4731bbbf9784db65de808d79f5cba04%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637153092918105515&sdata=VzVAcr4g7efpNK3CTtn1aVh9nJuqIerOVBiIAzyq1zI%3D&reserved=0>*
InvalidPathException: Illegal char (was: Building Royale project with
Maven throws NPE)
Posted by Piotr Zarzycki <pi...@gmail.com>.
It looks like I have two separate issues - apart of behavior when I'm
building application by Maven - I'm getting this using Moonshine.
In the morning this error points to different class. Now when I downloaded
newest Nightly build - it points to some PureMVC class.
: Internal error: java.nio.file.InvalidPathException: Illegal char <:> at
index 4:
file:///D:/Work/projects/Prominic.NET/ProminicNative/repository/puremvc-as3-multicore-framework/src/org/puremvc/as3/multicore/patterns/observer/Notifier.as
sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.SourceMap.addMapping(SourceMap.java:177)com.google.javascript.jscomp.CodePrinter$MappedCodePrinter.generateSourceMap(CodePrinter.java:141)com.google.javascript.jscomp.CodePrinter.toSource(CodePrinter.java:911)com.google.javascript.jscomp.CodePrinter.access$300(CodePrinter.java:42)com.google.javascript.jscomp.CodePrinter$Builder.build(CodePrinter.java:840)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2295)com.google.javascript.jscomp.Compiler.lambda$toSource$9(Compiler.java:2256)com.google.javascript.jscomp.Compiler$$Lambda$96.000000001354F550.call(Unknown
Source)com.google.javascript.jscomp.CompilerExecutor.runInCompilerThread(CompilerExecutor.java:129)com.google.javascript.jscomp.Compiler.runInCompilerThread(Compiler.java:876)com.google.javascript.jscomp.Compiler.toSource(Compiler.java:2218)com.google.javascript.jscomp.Compiler.lambda$toSource$7(Compiler.java:2175)com.google.javascript.jscomp.Compiler$$Lambda$95.0000000011211140.call(Unknown
Source)com.google.javascript.jscomp.CompilerExecutor$2.call(CompilerExecutor.java:102)java.util.concurrent.FutureTask.run(FutureTask.java:266)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)java.lang.Thread.run(Thread.java:813)
Thanks,
Piotr
śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Build is in progress. Once it's finish I will check ->
> https://builds.apache.org/job/Royale-compiler/1257/
>
> śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Hi Piotr,
>> latest commit seems to fix the problem. Let me know if all is now ok
>> sorry for the inconvenience
>> Carlos
>>
>> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
>> carlosrovira@apache.org>)
>> escribió:
>>
>> > Hi Piotr,
>> >
>> > I can see the problem is related to my latest commit in compiler to
>> solve
>> > the GOOG_HOME problem.
>> > going to fix it
>> >
>> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
>> carlosrovira@apache.org>)
>> > escribió:
>> >
>> >> Hi Piotr,
>> >>
>> >> ok, now I understand... It's clear that I broke something since trying
>> to
>> >> build now with Maven is generating the same issue ;)
>> >> I was focused on making build works for IDEs, that didn't test normal
>> >> maven path yesterday.
>> >> I'll be looking over it to find where is the problem
>> >> Sorry for the confusion! :)
>> >>
>> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
>> >> carlosrovira@apache.org>) escribió:
>> >>
>> >>> Hi Piotr,
>> >>>
>> >>> before understand the mistake, I downloaded and tested SDK from
>> Jenkins
>> >>> (build #2552 that was the latest created) and build TDJ with VSCode
>> and all
>> >>> worked ok (the same output as with Maven distribution created locally)
>> >>> Don't know if that report can be of help for you.
>> >>>
>> >>>
>> >>>
>> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
>> >>> piotrzarzycki21@gmail.com>) escribió:
>> >>>
>> >>>> Exactly we are not discussion any stuff related to distribution :) We
>> >>>> are
>> >>>> discussion at some point that maybe for some reason your changes
>> >>>> influence
>> >>>> somehow compiler or anything else which end up with above error.
>> Maybe
>> >>>> that
>> >>>> closure upgrade - I don't know. I look forward to hear more from
>> someone
>> >>>> what could know the reason of my issue.
>> >>>>
>> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
>> >>>> napisał(a):
>> >>>>
>> >>>> > Hi Piotr,
>> >>>> >
>> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
>> >>>> > piotrzarzycki21@gmail.com>) escribió:
>> >>>> >
>> >>>> > >
>> >>>> > >
>> >>>> > > Nope. Let's pretend that you have clean PC. You have downloaded
>> your
>> >>>> > Royale
>> >>>> > > application which contains pom.xml - You do "mvn clean install" -
>> >>>> All the
>> >>>> > > dependencies will be downloaded from Apache Maven Central
>> >>>> repository -
>> >>>> > > which is being updated by every build ->
>> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand
>> now
>> >>>> what
>> >>>> > > I'm
>> >>>> > > using now ?
>> >>>> > >
>> >>>> > >
>> >>>> > Ok, but in that case, you are not trying "distribution".... so
>> really
>> >>>> don't
>> >>>> > understand.
>> >>>> > I though we were discussing the new fixed distribution that
>> creates a
>> >>>> SDK
>> >>>> > in target folder or in the folder you specify (if use
>> >>>> > -DdistributionTargetFolder var)
>> >>>> > IOW, ant and maven continue to do the same as before, since
>> there's no
>> >>>> > changes out side of distribution (just class paths set ups for
>> maven
>> >>>> > generated artifacts that until now was empty or pointing to not
>> >>>> existing
>> >>>> > resources)
>> >>>> >
>> >>>> >
>> >>>> > > No I don't have to and I shouldn't have to - I'm using artifacts
>> >>>> from
>> >>>> > > Apache Maven Central.
>> >>>> > >
>> >>>> > >
>> >>>> > In that case you're not testing distribution. Jenkins builds the
>> same
>> >>>> as
>> >>>> > always. Other case will be if we can change Jenkins to build with
>> >>>> > distribution and then provide that SDK to download, that will be
>> the
>> >>>> proper
>> >>>> > way, and what the rest of projects using maven does in fact.
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > > --
>> >>>> > > Carlos Rovira
>> >>>> > > http://about.me/carlosrovira
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> >
>> >>>>
>> >>>>
>> >>>> --
>> >>>>
>> >>>> Piotr Zarzycki
>> >>>>
>> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
>> >>>> <https://www.patreon.com/piotrzarzycki>*
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> http://about.me/carlosrovira
>> >>>
>> >>>
>> >>
>> >> --
>> >> Carlos Rovira
>> >> http://about.me/carlosrovira
>> >>
>> >>
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>> >
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Right, I know it
El jue., 23 ene. 2020 a las 16:59, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> CRLF problem and build issue with ant distribution are two separate issues.
>
> czw., 23 sty 2020 o 16:39 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi,
> >
> > about maven distribution sdk I think it was before the good_home fix
> > about the other problem I think you refer to the CRFL problem, I really
> > don't know what could it be. Hope you get to the core of the problem
> >
> >
> > El jue., 23 ene. 2020 a las 16:33, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > Unfortunately building using [1] trough Moonshine still doesn't work.
> I'm
> > > looking into something to get more data.
> > > Still didn't check fully your Maven distribution, but first check was
> > > unsuccessful and Moonshine reported some messages which I need to
> check -
> > > why that happen.
> > >
> > > [1]
> > >
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/676/
> > >
> > > czw., 23 sty 2020 o 16:30 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > great to hear that :)
> > > > additionally I had confirmation from Josh that distribution SDK was
> as
> > > well
> > > > working for him.
> > > > So I think we got it :)
> > > >
> > > > El jue., 23 ene. 2020 a las 16:28, Piotr Zarzycki (<
> > > > piotrzarzycki21@gmail.com>) escribió:
> > > >
> > > > > Maven build for our application back to normal and I was able to
> > > produce
> > > > > release/debug files.
> > > > >
> > > > > śr., 22 sty 2020 o 16:05 Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > > > > napisał(a):
> > > > >
> > > > > > Build is in progress. Once it's finish I will check ->
> > > > > > https://builds.apache.org/job/Royale-compiler/1257/
> > > > > >
> > > > > > śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> > > > > > napisał(a):
> > > > > >
> > > > > >> Hi Piotr,
> > > > > >> latest commit seems to fix the problem. Let me know if all is
> now
> > ok
> > > > > >> sorry for the inconvenience
> > > > > >> Carlos
> > > > > >>
> > > > > >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> > > > > >> carlosrovira@apache.org>)
> > > > > >> escribió:
> > > > > >>
> > > > > >> > Hi Piotr,
> > > > > >> >
> > > > > >> > I can see the problem is related to my latest commit in
> compiler
> > > to
> > > > > >> solve
> > > > > >> > the GOOG_HOME problem.
> > > > > >> > going to fix it
> > > > > >> >
> > > > > >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> > > > > >> carlosrovira@apache.org>)
> > > > > >> > escribió:
> > > > > >> >
> > > > > >> >> Hi Piotr,
> > > > > >> >>
> > > > > >> >> ok, now I understand... It's clear that I broke something
> since
> > > > > trying
> > > > > >> to
> > > > > >> >> build now with Maven is generating the same issue ;)
> > > > > >> >> I was focused on making build works for IDEs, that didn't
> test
> > > > normal
> > > > > >> >> maven path yesterday.
> > > > > >> >> I'll be looking over it to find where is the problem
> > > > > >> >> Sorry for the confusion! :)
> > > > > >> >>
> > > > > >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> > > > > >> >> carlosrovira@apache.org>) escribió:
> > > > > >> >>
> > > > > >> >>> Hi Piotr,
> > > > > >> >>>
> > > > > >> >>> before understand the mistake, I downloaded and tested SDK
> > from
> > > > > >> Jenkins
> > > > > >> >>> (build #2552 that was the latest created) and build TDJ with
> > > > VSCode
> > > > > >> and all
> > > > > >> >>> worked ok (the same output as with Maven distribution
> created
> > > > > locally)
> > > > > >> >>> Don't know if that report can be of help for you.
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> > > > > >> >>> piotrzarzycki21@gmail.com>) escribió:
> > > > > >> >>>
> > > > > >> >>>> Exactly we are not discussion any stuff related to
> > distribution
> > > > :)
> > > > > We
> > > > > >> >>>> are
> > > > > >> >>>> discussion at some point that maybe for some reason your
> > > changes
> > > > > >> >>>> influence
> > > > > >> >>>> somehow compiler or anything else which end up with above
> > > error.
> > > > > >> Maybe
> > > > > >> >>>> that
> > > > > >> >>>> closure upgrade - I don't know. I look forward to hear more
> > > from
> > > > > >> someone
> > > > > >> >>>> what could know the reason of my issue.
> > > > > >> >>>>
> > > > > >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <
> > > carlosrovira@apache.org>
> > > > > >> >>>> napisał(a):
> > > > > >> >>>>
> > > > > >> >>>> > Hi Piotr,
> > > > > >> >>>> >
> > > > > >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> > > > > >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> > > > > >> >>>> >
> > > > > >> >>>> > >
> > > > > >> >>>> > >
> > > > > >> >>>> > > Nope. Let's pretend that you have clean PC. You have
> > > > downloaded
> > > > > >> your
> > > > > >> >>>> > Royale
> > > > > >> >>>> > > application which contains pom.xml - You do "mvn clean
> > > > > install" -
> > > > > >> >>>> All the
> > > > > >> >>>> > > dependencies will be downloaded from Apache Maven
> Central
> > > > > >> >>>> repository -
> > > > > >> >>>> > > which is being updated by every build ->
> > > > > >> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you
> > > > understand
> > > > > >> now
> > > > > >> >>>> what
> > > > > >> >>>> > > I'm
> > > > > >> >>>> > > using now ?
> > > > > >> >>>> > >
> > > > > >> >>>> > >
> > > > > >> >>>> > Ok, but in that case, you are not trying
> "distribution"....
> > > so
> > > > > >> really
> > > > > >> >>>> don't
> > > > > >> >>>> > understand.
> > > > > >> >>>> > I though we were discussing the new fixed distribution
> that
> > > > > >> creates a
> > > > > >> >>>> SDK
> > > > > >> >>>> > in target folder or in the folder you specify (if use
> > > > > >> >>>> > -DdistributionTargetFolder var)
> > > > > >> >>>> > IOW, ant and maven continue to do the same as before,
> since
> > > > > >> there's no
> > > > > >> >>>> > changes out side of distribution (just class paths set
> ups
> > > for
> > > > > >> maven
> > > > > >> >>>> > generated artifacts that until now was empty or pointing
> to
> > > not
> > > > > >> >>>> existing
> > > > > >> >>>> > resources)
> > > > > >> >>>> >
> > > > > >> >>>> >
> > > > > >> >>>> > > No I don't have to and I shouldn't have to - I'm using
> > > > > artifacts
> > > > > >> >>>> from
> > > > > >> >>>> > > Apache Maven Central.
> > > > > >> >>>> > >
> > > > > >> >>>> > >
> > > > > >> >>>> > In that case you're not testing distribution. Jenkins
> > builds
> > > > the
> > > > > >> same
> > > > > >> >>>> as
> > > > > >> >>>> > always. Other case will be if we can change Jenkins to
> > build
> > > > with
> > > > > >> >>>> > distribution and then provide that SDK to download, that
> > will
> > > > be
> > > > > >> the
> > > > > >> >>>> proper
> > > > > >> >>>> > way, and what the rest of projects using maven does in
> > fact.
> > > > > >> >>>> >
> > > > > >> >>>> >
> > > > > >> >>>> >
> > > > > >> >>>> >
> > > > > >> >>>> > > --
> > > > > >> >>>> > > Carlos Rovira
> > > > > >> >>>> > > http://about.me/carlosrovira
> > > > > >> >>>> > >
> > > > > >> >>>> > >
> > > > > >> >>>> > >
> > > > > >> >>>> > >
> > > > > >> >>>> >
> > > > > >> >>>>
> > > > > >> >>>>
> > > > > >> >>>> --
> > > > > >> >>>>
> > > > > >> >>>> Piotr Zarzycki
> > > > > >> >>>>
> > > > > >> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > >> >>>> <https://www.patreon.com/piotrzarzycki>*
> > > > > >> >>>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> --
> > > > > >> >>> Carlos Rovira
> > > > > >> >>> http://about.me/carlosrovira
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >> >> --
> > > > > >> >> Carlos Rovira
> > > > > >> >> http://about.me/carlosrovira
> > > > > >> >>
> > > > > >> >>
> > > > > >> >
> > > > > >> > --
> > > > > >> > Carlos Rovira
> > > > > >> > http://about.me/carlosrovira
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > > > >> --
> > > > > >> Carlos Rovira
> > > > > >> http://about.me/carlosrovira
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
CRLF problem and build issue with ant distribution are two separate issues.
czw., 23 sty 2020 o 16:39 Carlos Rovira <ca...@apache.org>
napisał(a):
> Hi,
>
> about maven distribution sdk I think it was before the good_home fix
> about the other problem I think you refer to the CRFL problem, I really
> don't know what could it be. Hope you get to the core of the problem
>
>
> El jue., 23 ene. 2020 a las 16:33, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Unfortunately building using [1] trough Moonshine still doesn't work. I'm
> > looking into something to get more data.
> > Still didn't check fully your Maven distribution, but first check was
> > unsuccessful and Moonshine reported some messages which I need to check -
> > why that happen.
> >
> > [1]
> >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/676/
> >
> > czw., 23 sty 2020 o 16:30 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > great to hear that :)
> > > additionally I had confirmation from Josh that distribution SDK was as
> > well
> > > working for him.
> > > So I think we got it :)
> > >
> > > El jue., 23 ene. 2020 a las 16:28, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > Maven build for our application back to normal and I was able to
> > produce
> > > > release/debug files.
> > > >
> > > > śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > Build is in progress. Once it's finish I will check ->
> > > > > https://builds.apache.org/job/Royale-compiler/1257/
> > > > >
> > > > > śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> > > > > napisał(a):
> > > > >
> > > > >> Hi Piotr,
> > > > >> latest commit seems to fix the problem. Let me know if all is now
> ok
> > > > >> sorry for the inconvenience
> > > > >> Carlos
> > > > >>
> > > > >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> > > > >> carlosrovira@apache.org>)
> > > > >> escribió:
> > > > >>
> > > > >> > Hi Piotr,
> > > > >> >
> > > > >> > I can see the problem is related to my latest commit in compiler
> > to
> > > > >> solve
> > > > >> > the GOOG_HOME problem.
> > > > >> > going to fix it
> > > > >> >
> > > > >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> > > > >> carlosrovira@apache.org>)
> > > > >> > escribió:
> > > > >> >
> > > > >> >> Hi Piotr,
> > > > >> >>
> > > > >> >> ok, now I understand... It's clear that I broke something since
> > > > trying
> > > > >> to
> > > > >> >> build now with Maven is generating the same issue ;)
> > > > >> >> I was focused on making build works for IDEs, that didn't test
> > > normal
> > > > >> >> maven path yesterday.
> > > > >> >> I'll be looking over it to find where is the problem
> > > > >> >> Sorry for the confusion! :)
> > > > >> >>
> > > > >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> > > > >> >> carlosrovira@apache.org>) escribió:
> > > > >> >>
> > > > >> >>> Hi Piotr,
> > > > >> >>>
> > > > >> >>> before understand the mistake, I downloaded and tested SDK
> from
> > > > >> Jenkins
> > > > >> >>> (build #2552 that was the latest created) and build TDJ with
> > > VSCode
> > > > >> and all
> > > > >> >>> worked ok (the same output as with Maven distribution created
> > > > locally)
> > > > >> >>> Don't know if that report can be of help for you.
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> > > > >> >>> piotrzarzycki21@gmail.com>) escribió:
> > > > >> >>>
> > > > >> >>>> Exactly we are not discussion any stuff related to
> distribution
> > > :)
> > > > We
> > > > >> >>>> are
> > > > >> >>>> discussion at some point that maybe for some reason your
> > changes
> > > > >> >>>> influence
> > > > >> >>>> somehow compiler or anything else which end up with above
> > error.
> > > > >> Maybe
> > > > >> >>>> that
> > > > >> >>>> closure upgrade - I don't know. I look forward to hear more
> > from
> > > > >> someone
> > > > >> >>>> what could know the reason of my issue.
> > > > >> >>>>
> > > > >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <
> > carlosrovira@apache.org>
> > > > >> >>>> napisał(a):
> > > > >> >>>>
> > > > >> >>>> > Hi Piotr,
> > > > >> >>>> >
> > > > >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> > > > >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> > > > >> >>>> >
> > > > >> >>>> > >
> > > > >> >>>> > >
> > > > >> >>>> > > Nope. Let's pretend that you have clean PC. You have
> > > downloaded
> > > > >> your
> > > > >> >>>> > Royale
> > > > >> >>>> > > application which contains pom.xml - You do "mvn clean
> > > > install" -
> > > > >> >>>> All the
> > > > >> >>>> > > dependencies will be downloaded from Apache Maven Central
> > > > >> >>>> repository -
> > > > >> >>>> > > which is being updated by every build ->
> > > > >> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you
> > > understand
> > > > >> now
> > > > >> >>>> what
> > > > >> >>>> > > I'm
> > > > >> >>>> > > using now ?
> > > > >> >>>> > >
> > > > >> >>>> > >
> > > > >> >>>> > Ok, but in that case, you are not trying "distribution"....
> > so
> > > > >> really
> > > > >> >>>> don't
> > > > >> >>>> > understand.
> > > > >> >>>> > I though we were discussing the new fixed distribution that
> > > > >> creates a
> > > > >> >>>> SDK
> > > > >> >>>> > in target folder or in the folder you specify (if use
> > > > >> >>>> > -DdistributionTargetFolder var)
> > > > >> >>>> > IOW, ant and maven continue to do the same as before, since
> > > > >> there's no
> > > > >> >>>> > changes out side of distribution (just class paths set ups
> > for
> > > > >> maven
> > > > >> >>>> > generated artifacts that until now was empty or pointing to
> > not
> > > > >> >>>> existing
> > > > >> >>>> > resources)
> > > > >> >>>> >
> > > > >> >>>> >
> > > > >> >>>> > > No I don't have to and I shouldn't have to - I'm using
> > > > artifacts
> > > > >> >>>> from
> > > > >> >>>> > > Apache Maven Central.
> > > > >> >>>> > >
> > > > >> >>>> > >
> > > > >> >>>> > In that case you're not testing distribution. Jenkins
> builds
> > > the
> > > > >> same
> > > > >> >>>> as
> > > > >> >>>> > always. Other case will be if we can change Jenkins to
> build
> > > with
> > > > >> >>>> > distribution and then provide that SDK to download, that
> will
> > > be
> > > > >> the
> > > > >> >>>> proper
> > > > >> >>>> > way, and what the rest of projects using maven does in
> fact.
> > > > >> >>>> >
> > > > >> >>>> >
> > > > >> >>>> >
> > > > >> >>>> >
> > > > >> >>>> > > --
> > > > >> >>>> > > Carlos Rovira
> > > > >> >>>> > > http://about.me/carlosrovira
> > > > >> >>>> > >
> > > > >> >>>> > >
> > > > >> >>>> > >
> > > > >> >>>> > >
> > > > >> >>>> >
> > > > >> >>>>
> > > > >> >>>>
> > > > >> >>>> --
> > > > >> >>>>
> > > > >> >>>> Piotr Zarzycki
> > > > >> >>>>
> > > > >> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> >>>> <https://www.patreon.com/piotrzarzycki>*
> > > > >> >>>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> --
> > > > >> >>> Carlos Rovira
> > > > >> >>> http://about.me/carlosrovira
> > > > >> >>>
> > > > >> >>>
> > > > >> >>
> > > > >> >> --
> > > > >> >> Carlos Rovira
> > > > >> >> http://about.me/carlosrovira
> > > > >> >>
> > > > >> >>
> > > > >> >
> > > > >> > --
> > > > >> > Carlos Rovira
> > > > >> > http://about.me/carlosrovira
> > > > >> >
> > > > >> >
> > > > >>
> > > > >> --
> > > > >> Carlos Rovira
> > > > >> http://about.me/carlosrovira
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
about maven distribution sdk I think it was before the good_home fix
about the other problem I think you refer to the CRFL problem, I really
don't know what could it be. Hope you get to the core of the problem
El jue., 23 ene. 2020 a las 16:33, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Unfortunately building using [1] trough Moonshine still doesn't work. I'm
> looking into something to get more data.
> Still didn't check fully your Maven distribution, but first check was
> unsuccessful and Moonshine reported some messages which I need to check -
> why that happen.
>
> [1]
>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/676/
>
> czw., 23 sty 2020 o 16:30 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Piotr,
> >
> > great to hear that :)
> > additionally I had confirmation from Josh that distribution SDK was as
> well
> > working for him.
> > So I think we got it :)
> >
> > El jue., 23 ene. 2020 a las 16:28, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > Maven build for our application back to normal and I was able to
> produce
> > > release/debug files.
> > >
> > > śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
> > > napisał(a):
> > >
> > > > Build is in progress. Once it's finish I will check ->
> > > > https://builds.apache.org/job/Royale-compiler/1257/
> > > >
> > > > śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> > > > napisał(a):
> > > >
> > > >> Hi Piotr,
> > > >> latest commit seems to fix the problem. Let me know if all is now ok
> > > >> sorry for the inconvenience
> > > >> Carlos
> > > >>
> > > >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> > > >> carlosrovira@apache.org>)
> > > >> escribió:
> > > >>
> > > >> > Hi Piotr,
> > > >> >
> > > >> > I can see the problem is related to my latest commit in compiler
> to
> > > >> solve
> > > >> > the GOOG_HOME problem.
> > > >> > going to fix it
> > > >> >
> > > >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> > > >> carlosrovira@apache.org>)
> > > >> > escribió:
> > > >> >
> > > >> >> Hi Piotr,
> > > >> >>
> > > >> >> ok, now I understand... It's clear that I broke something since
> > > trying
> > > >> to
> > > >> >> build now with Maven is generating the same issue ;)
> > > >> >> I was focused on making build works for IDEs, that didn't test
> > normal
> > > >> >> maven path yesterday.
> > > >> >> I'll be looking over it to find where is the problem
> > > >> >> Sorry for the confusion! :)
> > > >> >>
> > > >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> > > >> >> carlosrovira@apache.org>) escribió:
> > > >> >>
> > > >> >>> Hi Piotr,
> > > >> >>>
> > > >> >>> before understand the mistake, I downloaded and tested SDK from
> > > >> Jenkins
> > > >> >>> (build #2552 that was the latest created) and build TDJ with
> > VSCode
> > > >> and all
> > > >> >>> worked ok (the same output as with Maven distribution created
> > > locally)
> > > >> >>> Don't know if that report can be of help for you.
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> > > >> >>> piotrzarzycki21@gmail.com>) escribió:
> > > >> >>>
> > > >> >>>> Exactly we are not discussion any stuff related to distribution
> > :)
> > > We
> > > >> >>>> are
> > > >> >>>> discussion at some point that maybe for some reason your
> changes
> > > >> >>>> influence
> > > >> >>>> somehow compiler or anything else which end up with above
> error.
> > > >> Maybe
> > > >> >>>> that
> > > >> >>>> closure upgrade - I don't know. I look forward to hear more
> from
> > > >> someone
> > > >> >>>> what could know the reason of my issue.
> > > >> >>>>
> > > >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <
> carlosrovira@apache.org>
> > > >> >>>> napisał(a):
> > > >> >>>>
> > > >> >>>> > Hi Piotr,
> > > >> >>>> >
> > > >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> > > >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> > > >> >>>> >
> > > >> >>>> > >
> > > >> >>>> > >
> > > >> >>>> > > Nope. Let's pretend that you have clean PC. You have
> > downloaded
> > > >> your
> > > >> >>>> > Royale
> > > >> >>>> > > application which contains pom.xml - You do "mvn clean
> > > install" -
> > > >> >>>> All the
> > > >> >>>> > > dependencies will be downloaded from Apache Maven Central
> > > >> >>>> repository -
> > > >> >>>> > > which is being updated by every build ->
> > > >> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you
> > understand
> > > >> now
> > > >> >>>> what
> > > >> >>>> > > I'm
> > > >> >>>> > > using now ?
> > > >> >>>> > >
> > > >> >>>> > >
> > > >> >>>> > Ok, but in that case, you are not trying "distribution"....
> so
> > > >> really
> > > >> >>>> don't
> > > >> >>>> > understand.
> > > >> >>>> > I though we were discussing the new fixed distribution that
> > > >> creates a
> > > >> >>>> SDK
> > > >> >>>> > in target folder or in the folder you specify (if use
> > > >> >>>> > -DdistributionTargetFolder var)
> > > >> >>>> > IOW, ant and maven continue to do the same as before, since
> > > >> there's no
> > > >> >>>> > changes out side of distribution (just class paths set ups
> for
> > > >> maven
> > > >> >>>> > generated artifacts that until now was empty or pointing to
> not
> > > >> >>>> existing
> > > >> >>>> > resources)
> > > >> >>>> >
> > > >> >>>> >
> > > >> >>>> > > No I don't have to and I shouldn't have to - I'm using
> > > artifacts
> > > >> >>>> from
> > > >> >>>> > > Apache Maven Central.
> > > >> >>>> > >
> > > >> >>>> > >
> > > >> >>>> > In that case you're not testing distribution. Jenkins builds
> > the
> > > >> same
> > > >> >>>> as
> > > >> >>>> > always. Other case will be if we can change Jenkins to build
> > with
> > > >> >>>> > distribution and then provide that SDK to download, that will
> > be
> > > >> the
> > > >> >>>> proper
> > > >> >>>> > way, and what the rest of projects using maven does in fact.
> > > >> >>>> >
> > > >> >>>> >
> > > >> >>>> >
> > > >> >>>> >
> > > >> >>>> > > --
> > > >> >>>> > > Carlos Rovira
> > > >> >>>> > > http://about.me/carlosrovira
> > > >> >>>> > >
> > > >> >>>> > >
> > > >> >>>> > >
> > > >> >>>> > >
> > > >> >>>> >
> > > >> >>>>
> > > >> >>>>
> > > >> >>>> --
> > > >> >>>>
> > > >> >>>> Piotr Zarzycki
> > > >> >>>>
> > > >> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> >>>> <https://www.patreon.com/piotrzarzycki>*
> > > >> >>>>
> > > >> >>>
> > > >> >>>
> > > >> >>> --
> > > >> >>> Carlos Rovira
> > > >> >>> http://about.me/carlosrovira
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >> >> --
> > > >> >> Carlos Rovira
> > > >> >> http://about.me/carlosrovira
> > > >> >>
> > > >> >>
> > > >> >
> > > >> > --
> > > >> > Carlos Rovira
> > > >> > http://about.me/carlosrovira
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >> Carlos Rovira
> > > >> http://about.me/carlosrovira
> > > >>
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Unfortunately building using [1] trough Moonshine still doesn't work. I'm
looking into something to get more data.
Still didn't check fully your Maven distribution, but first check was
unsuccessful and Moonshine reported some messages which I need to check -
why that happen.
[1]
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/676/
czw., 23 sty 2020 o 16:30 Carlos Rovira <ca...@apache.org>
napisał(a):
> Hi Piotr,
>
> great to hear that :)
> additionally I had confirmation from Josh that distribution SDK was as well
> working for him.
> So I think we got it :)
>
> El jue., 23 ene. 2020 a las 16:28, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Maven build for our application back to normal and I was able to produce
> > release/debug files.
> >
> > śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> > > Build is in progress. Once it's finish I will check ->
> > > https://builds.apache.org/job/Royale-compiler/1257/
> > >
> > > śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > >> Hi Piotr,
> > >> latest commit seems to fix the problem. Let me know if all is now ok
> > >> sorry for the inconvenience
> > >> Carlos
> > >>
> > >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> > >> carlosrovira@apache.org>)
> > >> escribió:
> > >>
> > >> > Hi Piotr,
> > >> >
> > >> > I can see the problem is related to my latest commit in compiler to
> > >> solve
> > >> > the GOOG_HOME problem.
> > >> > going to fix it
> > >> >
> > >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> > >> carlosrovira@apache.org>)
> > >> > escribió:
> > >> >
> > >> >> Hi Piotr,
> > >> >>
> > >> >> ok, now I understand... It's clear that I broke something since
> > trying
> > >> to
> > >> >> build now with Maven is generating the same issue ;)
> > >> >> I was focused on making build works for IDEs, that didn't test
> normal
> > >> >> maven path yesterday.
> > >> >> I'll be looking over it to find where is the problem
> > >> >> Sorry for the confusion! :)
> > >> >>
> > >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> > >> >> carlosrovira@apache.org>) escribió:
> > >> >>
> > >> >>> Hi Piotr,
> > >> >>>
> > >> >>> before understand the mistake, I downloaded and tested SDK from
> > >> Jenkins
> > >> >>> (build #2552 that was the latest created) and build TDJ with
> VSCode
> > >> and all
> > >> >>> worked ok (the same output as with Maven distribution created
> > locally)
> > >> >>> Don't know if that report can be of help for you.
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> > >> >>> piotrzarzycki21@gmail.com>) escribió:
> > >> >>>
> > >> >>>> Exactly we are not discussion any stuff related to distribution
> :)
> > We
> > >> >>>> are
> > >> >>>> discussion at some point that maybe for some reason your changes
> > >> >>>> influence
> > >> >>>> somehow compiler or anything else which end up with above error.
> > >> Maybe
> > >> >>>> that
> > >> >>>> closure upgrade - I don't know. I look forward to hear more from
> > >> someone
> > >> >>>> what could know the reason of my issue.
> > >> >>>>
> > >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
> > >> >>>> napisał(a):
> > >> >>>>
> > >> >>>> > Hi Piotr,
> > >> >>>> >
> > >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> > >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> > >> >>>> >
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > > Nope. Let's pretend that you have clean PC. You have
> downloaded
> > >> your
> > >> >>>> > Royale
> > >> >>>> > > application which contains pom.xml - You do "mvn clean
> > install" -
> > >> >>>> All the
> > >> >>>> > > dependencies will be downloaded from Apache Maven Central
> > >> >>>> repository -
> > >> >>>> > > which is being updated by every build ->
> > >> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you
> understand
> > >> now
> > >> >>>> what
> > >> >>>> > > I'm
> > >> >>>> > > using now ?
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > Ok, but in that case, you are not trying "distribution".... so
> > >> really
> > >> >>>> don't
> > >> >>>> > understand.
> > >> >>>> > I though we were discussing the new fixed distribution that
> > >> creates a
> > >> >>>> SDK
> > >> >>>> > in target folder or in the folder you specify (if use
> > >> >>>> > -DdistributionTargetFolder var)
> > >> >>>> > IOW, ant and maven continue to do the same as before, since
> > >> there's no
> > >> >>>> > changes out side of distribution (just class paths set ups for
> > >> maven
> > >> >>>> > generated artifacts that until now was empty or pointing to not
> > >> >>>> existing
> > >> >>>> > resources)
> > >> >>>> >
> > >> >>>> >
> > >> >>>> > > No I don't have to and I shouldn't have to - I'm using
> > artifacts
> > >> >>>> from
> > >> >>>> > > Apache Maven Central.
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > In that case you're not testing distribution. Jenkins builds
> the
> > >> same
> > >> >>>> as
> > >> >>>> > always. Other case will be if we can change Jenkins to build
> with
> > >> >>>> > distribution and then provide that SDK to download, that will
> be
> > >> the
> > >> >>>> proper
> > >> >>>> > way, and what the rest of projects using maven does in fact.
> > >> >>>> >
> > >> >>>> >
> > >> >>>> >
> > >> >>>> >
> > >> >>>> > > --
> > >> >>>> > > Carlos Rovira
> > >> >>>> > > http://about.me/carlosrovira
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> > >
> > >> >>>> >
> > >> >>>>
> > >> >>>>
> > >> >>>> --
> > >> >>>>
> > >> >>>> Piotr Zarzycki
> > >> >>>>
> > >> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> >>>> <https://www.patreon.com/piotrzarzycki>*
> > >> >>>>
> > >> >>>
> > >> >>>
> > >> >>> --
> > >> >>> Carlos Rovira
> > >> >>> http://about.me/carlosrovira
> > >> >>>
> > >> >>>
> > >> >>
> > >> >> --
> > >> >> Carlos Rovira
> > >> >> http://about.me/carlosrovira
> > >> >>
> > >> >>
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> > http://about.me/carlosrovira
> > >> >
> > >> >
> > >>
> > >> --
> > >> Carlos Rovira
> > >> http://about.me/carlosrovira
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
great to hear that :)
additionally I had confirmation from Josh that distribution SDK was as well
working for him.
So I think we got it :)
El jue., 23 ene. 2020 a las 16:28, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Maven build for our application back to normal and I was able to produce
> release/debug files.
>
> śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Build is in progress. Once it's finish I will check ->
> > https://builds.apache.org/job/Royale-compiler/1257/
> >
> > śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> Hi Piotr,
> >> latest commit seems to fix the problem. Let me know if all is now ok
> >> sorry for the inconvenience
> >> Carlos
> >>
> >> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >> escribió:
> >>
> >> > Hi Piotr,
> >> >
> >> > I can see the problem is related to my latest commit in compiler to
> >> solve
> >> > the GOOG_HOME problem.
> >> > going to fix it
> >> >
> >> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >> > escribió:
> >> >
> >> >> Hi Piotr,
> >> >>
> >> >> ok, now I understand... It's clear that I broke something since
> trying
> >> to
> >> >> build now with Maven is generating the same issue ;)
> >> >> I was focused on making build works for IDEs, that didn't test normal
> >> >> maven path yesterday.
> >> >> I'll be looking over it to find where is the problem
> >> >> Sorry for the confusion! :)
> >> >>
> >> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> >> >> carlosrovira@apache.org>) escribió:
> >> >>
> >> >>> Hi Piotr,
> >> >>>
> >> >>> before understand the mistake, I downloaded and tested SDK from
> >> Jenkins
> >> >>> (build #2552 that was the latest created) and build TDJ with VSCode
> >> and all
> >> >>> worked ok (the same output as with Maven distribution created
> locally)
> >> >>> Don't know if that report can be of help for you.
> >> >>>
> >> >>>
> >> >>>
> >> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> >> >>> piotrzarzycki21@gmail.com>) escribió:
> >> >>>
> >> >>>> Exactly we are not discussion any stuff related to distribution :)
> We
> >> >>>> are
> >> >>>> discussion at some point that maybe for some reason your changes
> >> >>>> influence
> >> >>>> somehow compiler or anything else which end up with above error.
> >> Maybe
> >> >>>> that
> >> >>>> closure upgrade - I don't know. I look forward to hear more from
> >> someone
> >> >>>> what could know the reason of my issue.
> >> >>>>
> >> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
> >> >>>> napisał(a):
> >> >>>>
> >> >>>> > Hi Piotr,
> >> >>>> >
> >> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> >> >>>> > piotrzarzycki21@gmail.com>) escribió:
> >> >>>> >
> >> >>>> > >
> >> >>>> > >
> >> >>>> > > Nope. Let's pretend that you have clean PC. You have downloaded
> >> your
> >> >>>> > Royale
> >> >>>> > > application which contains pom.xml - You do "mvn clean
> install" -
> >> >>>> All the
> >> >>>> > > dependencies will be downloaded from Apache Maven Central
> >> >>>> repository -
> >> >>>> > > which is being updated by every build ->
> >> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand
> >> now
> >> >>>> what
> >> >>>> > > I'm
> >> >>>> > > using now ?
> >> >>>> > >
> >> >>>> > >
> >> >>>> > Ok, but in that case, you are not trying "distribution".... so
> >> really
> >> >>>> don't
> >> >>>> > understand.
> >> >>>> > I though we were discussing the new fixed distribution that
> >> creates a
> >> >>>> SDK
> >> >>>> > in target folder or in the folder you specify (if use
> >> >>>> > -DdistributionTargetFolder var)
> >> >>>> > IOW, ant and maven continue to do the same as before, since
> >> there's no
> >> >>>> > changes out side of distribution (just class paths set ups for
> >> maven
> >> >>>> > generated artifacts that until now was empty or pointing to not
> >> >>>> existing
> >> >>>> > resources)
> >> >>>> >
> >> >>>> >
> >> >>>> > > No I don't have to and I shouldn't have to - I'm using
> artifacts
> >> >>>> from
> >> >>>> > > Apache Maven Central.
> >> >>>> > >
> >> >>>> > >
> >> >>>> > In that case you're not testing distribution. Jenkins builds the
> >> same
> >> >>>> as
> >> >>>> > always. Other case will be if we can change Jenkins to build with
> >> >>>> > distribution and then provide that SDK to download, that will be
> >> the
> >> >>>> proper
> >> >>>> > way, and what the rest of projects using maven does in fact.
> >> >>>> >
> >> >>>> >
> >> >>>> >
> >> >>>> >
> >> >>>> > > --
> >> >>>> > > Carlos Rovira
> >> >>>> > > http://about.me/carlosrovira
> >> >>>> > >
> >> >>>> > >
> >> >>>> > >
> >> >>>> > >
> >> >>>> >
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>>
> >> >>>> Piotr Zarzycki
> >> >>>>
> >> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> >> >>>> <https://www.patreon.com/piotrzarzycki>*
> >> >>>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Carlos Rovira
> >> >>> http://about.me/carlosrovira
> >> >>>
> >> >>>
> >> >>
> >> >> --
> >> >> Carlos Rovira
> >> >> http://about.me/carlosrovira
> >> >>
> >> >>
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >> >
> >> >
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Maven build for our application back to normal and I was able to produce
release/debug files.
śr., 22 sty 2020 o 16:05 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Build is in progress. Once it's finish I will check ->
> https://builds.apache.org/job/Royale-compiler/1257/
>
> śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Hi Piotr,
>> latest commit seems to fix the problem. Let me know if all is now ok
>> sorry for the inconvenience
>> Carlos
>>
>> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<
>> carlosrovira@apache.org>)
>> escribió:
>>
>> > Hi Piotr,
>> >
>> > I can see the problem is related to my latest commit in compiler to
>> solve
>> > the GOOG_HOME problem.
>> > going to fix it
>> >
>> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
>> carlosrovira@apache.org>)
>> > escribió:
>> >
>> >> Hi Piotr,
>> >>
>> >> ok, now I understand... It's clear that I broke something since trying
>> to
>> >> build now with Maven is generating the same issue ;)
>> >> I was focused on making build works for IDEs, that didn't test normal
>> >> maven path yesterday.
>> >> I'll be looking over it to find where is the problem
>> >> Sorry for the confusion! :)
>> >>
>> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
>> >> carlosrovira@apache.org>) escribió:
>> >>
>> >>> Hi Piotr,
>> >>>
>> >>> before understand the mistake, I downloaded and tested SDK from
>> Jenkins
>> >>> (build #2552 that was the latest created) and build TDJ with VSCode
>> and all
>> >>> worked ok (the same output as with Maven distribution created locally)
>> >>> Don't know if that report can be of help for you.
>> >>>
>> >>>
>> >>>
>> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
>> >>> piotrzarzycki21@gmail.com>) escribió:
>> >>>
>> >>>> Exactly we are not discussion any stuff related to distribution :) We
>> >>>> are
>> >>>> discussion at some point that maybe for some reason your changes
>> >>>> influence
>> >>>> somehow compiler or anything else which end up with above error.
>> Maybe
>> >>>> that
>> >>>> closure upgrade - I don't know. I look forward to hear more from
>> someone
>> >>>> what could know the reason of my issue.
>> >>>>
>> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
>> >>>> napisał(a):
>> >>>>
>> >>>> > Hi Piotr,
>> >>>> >
>> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
>> >>>> > piotrzarzycki21@gmail.com>) escribió:
>> >>>> >
>> >>>> > >
>> >>>> > >
>> >>>> > > Nope. Let's pretend that you have clean PC. You have downloaded
>> your
>> >>>> > Royale
>> >>>> > > application which contains pom.xml - You do "mvn clean install" -
>> >>>> All the
>> >>>> > > dependencies will be downloaded from Apache Maven Central
>> >>>> repository -
>> >>>> > > which is being updated by every build ->
>> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand
>> now
>> >>>> what
>> >>>> > > I'm
>> >>>> > > using now ?
>> >>>> > >
>> >>>> > >
>> >>>> > Ok, but in that case, you are not trying "distribution".... so
>> really
>> >>>> don't
>> >>>> > understand.
>> >>>> > I though we were discussing the new fixed distribution that
>> creates a
>> >>>> SDK
>> >>>> > in target folder or in the folder you specify (if use
>> >>>> > -DdistributionTargetFolder var)
>> >>>> > IOW, ant and maven continue to do the same as before, since
>> there's no
>> >>>> > changes out side of distribution (just class paths set ups for
>> maven
>> >>>> > generated artifacts that until now was empty or pointing to not
>> >>>> existing
>> >>>> > resources)
>> >>>> >
>> >>>> >
>> >>>> > > No I don't have to and I shouldn't have to - I'm using artifacts
>> >>>> from
>> >>>> > > Apache Maven Central.
>> >>>> > >
>> >>>> > >
>> >>>> > In that case you're not testing distribution. Jenkins builds the
>> same
>> >>>> as
>> >>>> > always. Other case will be if we can change Jenkins to build with
>> >>>> > distribution and then provide that SDK to download, that will be
>> the
>> >>>> proper
>> >>>> > way, and what the rest of projects using maven does in fact.
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > > --
>> >>>> > > Carlos Rovira
>> >>>> > > http://about.me/carlosrovira
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> >
>> >>>>
>> >>>>
>> >>>> --
>> >>>>
>> >>>> Piotr Zarzycki
>> >>>>
>> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
>> >>>> <https://www.patreon.com/piotrzarzycki>*
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> http://about.me/carlosrovira
>> >>>
>> >>>
>> >>
>> >> --
>> >> Carlos Rovira
>> >> http://about.me/carlosrovira
>> >>
>> >>
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>> >
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Build is in progress. Once it's finish I will check ->
https://builds.apache.org/job/Royale-compiler/1257/
śr., 22 sty 2020 o 15:54 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Piotr,
> latest commit seems to fix the problem. Let me know if all is now ok
> sorry for the inconvenience
> Carlos
>
> El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<carlosrovira@apache.org
> >)
> escribió:
>
> > Hi Piotr,
> >
> > I can see the problem is related to my latest commit in compiler to solve
> > the GOOG_HOME problem.
> > going to fix it
> >
> > El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<
> carlosrovira@apache.org>)
> > escribió:
> >
> >> Hi Piotr,
> >>
> >> ok, now I understand... It's clear that I broke something since trying
> to
> >> build now with Maven is generating the same issue ;)
> >> I was focused on making build works for IDEs, that didn't test normal
> >> maven path yesterday.
> >> I'll be looking over it to find where is the problem
> >> Sorry for the confusion! :)
> >>
> >> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
> >> carlosrovira@apache.org>) escribió:
> >>
> >>> Hi Piotr,
> >>>
> >>> before understand the mistake, I downloaded and tested SDK from Jenkins
> >>> (build #2552 that was the latest created) and build TDJ with VSCode
> and all
> >>> worked ok (the same output as with Maven distribution created locally)
> >>> Don't know if that report can be of help for you.
> >>>
> >>>
> >>>
> >>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> >>> piotrzarzycki21@gmail.com>) escribió:
> >>>
> >>>> Exactly we are not discussion any stuff related to distribution :) We
> >>>> are
> >>>> discussion at some point that maybe for some reason your changes
> >>>> influence
> >>>> somehow compiler or anything else which end up with above error. Maybe
> >>>> that
> >>>> closure upgrade - I don't know. I look forward to hear more from
> someone
> >>>> what could know the reason of my issue.
> >>>>
> >>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
> >>>> napisał(a):
> >>>>
> >>>> > Hi Piotr,
> >>>> >
> >>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> >>>> > piotrzarzycki21@gmail.com>) escribió:
> >>>> >
> >>>> > >
> >>>> > >
> >>>> > > Nope. Let's pretend that you have clean PC. You have downloaded
> your
> >>>> > Royale
> >>>> > > application which contains pom.xml - You do "mvn clean install" -
> >>>> All the
> >>>> > > dependencies will be downloaded from Apache Maven Central
> >>>> repository -
> >>>> > > which is being updated by every build ->
> >>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand
> now
> >>>> what
> >>>> > > I'm
> >>>> > > using now ?
> >>>> > >
> >>>> > >
> >>>> > Ok, but in that case, you are not trying "distribution".... so
> really
> >>>> don't
> >>>> > understand.
> >>>> > I though we were discussing the new fixed distribution that creates
> a
> >>>> SDK
> >>>> > in target folder or in the folder you specify (if use
> >>>> > -DdistributionTargetFolder var)
> >>>> > IOW, ant and maven continue to do the same as before, since there's
> no
> >>>> > changes out side of distribution (just class paths set ups for maven
> >>>> > generated artifacts that until now was empty or pointing to not
> >>>> existing
> >>>> > resources)
> >>>> >
> >>>> >
> >>>> > > No I don't have to and I shouldn't have to - I'm using artifacts
> >>>> from
> >>>> > > Apache Maven Central.
> >>>> > >
> >>>> > >
> >>>> > In that case you're not testing distribution. Jenkins builds the
> same
> >>>> as
> >>>> > always. Other case will be if we can change Jenkins to build with
> >>>> > distribution and then provide that SDK to download, that will be the
> >>>> proper
> >>>> > way, and what the rest of projects using maven does in fact.
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > > --
> >>>> > > Carlos Rovira
> >>>> > > http://about.me/carlosrovira
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> >
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Piotr Zarzycki
> >>>>
> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> >>>> <https://www.patreon.com/piotrzarzycki>*
> >>>>
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>>
> >>>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
latest commit seems to fix the problem. Let me know if all is now ok
sorry for the inconvenience
Carlos
El mié., 22 ene. 2020 a las 13:51, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi Piotr,
>
> I can see the problem is related to my latest commit in compiler to solve
> the GOOG_HOME problem.
> going to fix it
>
> El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<ca...@apache.org>)
> escribió:
>
>> Hi Piotr,
>>
>> ok, now I understand... It's clear that I broke something since trying to
>> build now with Maven is generating the same issue ;)
>> I was focused on making build works for IDEs, that didn't test normal
>> maven path yesterday.
>> I'll be looking over it to find where is the problem
>> Sorry for the confusion! :)
>>
>> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<
>> carlosrovira@apache.org>) escribió:
>>
>>> Hi Piotr,
>>>
>>> before understand the mistake, I downloaded and tested SDK from Jenkins
>>> (build #2552 that was the latest created) and build TDJ with VSCode and all
>>> worked ok (the same output as with Maven distribution created locally)
>>> Don't know if that report can be of help for you.
>>>
>>>
>>>
>>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
>>> piotrzarzycki21@gmail.com>) escribió:
>>>
>>>> Exactly we are not discussion any stuff related to distribution :) We
>>>> are
>>>> discussion at some point that maybe for some reason your changes
>>>> influence
>>>> somehow compiler or anything else which end up with above error. Maybe
>>>> that
>>>> closure upgrade - I don't know. I look forward to hear more from someone
>>>> what could know the reason of my issue.
>>>>
>>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
>>>> napisał(a):
>>>>
>>>> > Hi Piotr,
>>>> >
>>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
>>>> > piotrzarzycki21@gmail.com>) escribió:
>>>> >
>>>> > >
>>>> > >
>>>> > > Nope. Let's pretend that you have clean PC. You have downloaded your
>>>> > Royale
>>>> > > application which contains pom.xml - You do "mvn clean install" -
>>>> All the
>>>> > > dependencies will be downloaded from Apache Maven Central
>>>> repository -
>>>> > > which is being updated by every build ->
>>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand now
>>>> what
>>>> > > I'm
>>>> > > using now ?
>>>> > >
>>>> > >
>>>> > Ok, but in that case, you are not trying "distribution".... so really
>>>> don't
>>>> > understand.
>>>> > I though we were discussing the new fixed distribution that creates a
>>>> SDK
>>>> > in target folder or in the folder you specify (if use
>>>> > -DdistributionTargetFolder var)
>>>> > IOW, ant and maven continue to do the same as before, since there's no
>>>> > changes out side of distribution (just class paths set ups for maven
>>>> > generated artifacts that until now was empty or pointing to not
>>>> existing
>>>> > resources)
>>>> >
>>>> >
>>>> > > No I don't have to and I shouldn't have to - I'm using artifacts
>>>> from
>>>> > > Apache Maven Central.
>>>> > >
>>>> > >
>>>> > In that case you're not testing distribution. Jenkins builds the same
>>>> as
>>>> > always. Other case will be if we can change Jenkins to build with
>>>> > distribution and then provide that SDK to download, that will be the
>>>> proper
>>>> > way, and what the rest of projects using maven does in fact.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > > --
>>>> > > Carlos Rovira
>>>> > > http://about.me/carlosrovira
>>>> > >
>>>> > >
>>>> > >
>>>> > >
>>>> >
>>>>
>>>>
>>>> --
>>>>
>>>> Piotr Zarzycki
>>>>
>>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>>> <https://www.patreon.com/piotrzarzycki>*
>>>>
>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
I can see the problem is related to my latest commit in compiler to solve
the GOOG_HOME problem.
going to fix it
El mié., 22 ene. 2020 a las 13:31, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi Piotr,
>
> ok, now I understand... It's clear that I broke something since trying to
> build now with Maven is generating the same issue ;)
> I was focused on making build works for IDEs, that didn't test normal
> maven path yesterday.
> I'll be looking over it to find where is the problem
> Sorry for the confusion! :)
>
> El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<ca...@apache.org>)
> escribió:
>
>> Hi Piotr,
>>
>> before understand the mistake, I downloaded and tested SDK from Jenkins
>> (build #2552 that was the latest created) and build TDJ with VSCode and all
>> worked ok (the same output as with Maven distribution created locally)
>> Don't know if that report can be of help for you.
>>
>>
>>
>> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
>> piotrzarzycki21@gmail.com>) escribió:
>>
>>> Exactly we are not discussion any stuff related to distribution :) We are
>>> discussion at some point that maybe for some reason your changes
>>> influence
>>> somehow compiler or anything else which end up with above error. Maybe
>>> that
>>> closure upgrade - I don't know. I look forward to hear more from someone
>>> what could know the reason of my issue.
>>>
>>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
>>> napisał(a):
>>>
>>> > Hi Piotr,
>>> >
>>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
>>> > piotrzarzycki21@gmail.com>) escribió:
>>> >
>>> > >
>>> > >
>>> > > Nope. Let's pretend that you have clean PC. You have downloaded your
>>> > Royale
>>> > > application which contains pom.xml - You do "mvn clean install" -
>>> All the
>>> > > dependencies will be downloaded from Apache Maven Central repository
>>> -
>>> > > which is being updated by every build ->
>>> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand now
>>> what
>>> > > I'm
>>> > > using now ?
>>> > >
>>> > >
>>> > Ok, but in that case, you are not trying "distribution".... so really
>>> don't
>>> > understand.
>>> > I though we were discussing the new fixed distribution that creates a
>>> SDK
>>> > in target folder or in the folder you specify (if use
>>> > -DdistributionTargetFolder var)
>>> > IOW, ant and maven continue to do the same as before, since there's no
>>> > changes out side of distribution (just class paths set ups for maven
>>> > generated artifacts that until now was empty or pointing to not
>>> existing
>>> > resources)
>>> >
>>> >
>>> > > No I don't have to and I shouldn't have to - I'm using artifacts from
>>> > > Apache Maven Central.
>>> > >
>>> > >
>>> > In that case you're not testing distribution. Jenkins builds the same
>>> as
>>> > always. Other case will be if we can change Jenkins to build with
>>> > distribution and then provide that SDK to download, that will be the
>>> proper
>>> > way, and what the rest of projects using maven does in fact.
>>> >
>>> >
>>> >
>>> >
>>> > > --
>>> > > Carlos Rovira
>>> > > http://about.me/carlosrovira
>>> > >
>>> > >
>>> > >
>>> > >
>>> >
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> <https://www.patreon.com/piotrzarzycki>*
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
ok, now I understand... It's clear that I broke something since trying to
build now with Maven is generating the same issue ;)
I was focused on making build works for IDEs, that didn't test normal maven
path yesterday.
I'll be looking over it to find where is the problem
Sorry for the confusion! :)
El mié., 22 ene. 2020 a las 13:27, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi Piotr,
>
> before understand the mistake, I downloaded and tested SDK from Jenkins
> (build #2552 that was the latest created) and build TDJ with VSCode and all
> worked ok (the same output as with Maven distribution created locally)
> Don't know if that report can be of help for you.
>
>
>
> El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
>> Exactly we are not discussion any stuff related to distribution :) We are
>> discussion at some point that maybe for some reason your changes influence
>> somehow compiler or anything else which end up with above error. Maybe
>> that
>> closure upgrade - I don't know. I look forward to hear more from someone
>> what could know the reason of my issue.
>>
>> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
>> napisał(a):
>>
>> > Hi Piotr,
>> >
>> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
>> > piotrzarzycki21@gmail.com>) escribió:
>> >
>> > >
>> > >
>> > > Nope. Let's pretend that you have clean PC. You have downloaded your
>> > Royale
>> > > application which contains pom.xml - You do "mvn clean install" - All
>> the
>> > > dependencies will be downloaded from Apache Maven Central repository -
>> > > which is being updated by every build ->
>> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand now
>> what
>> > > I'm
>> > > using now ?
>> > >
>> > >
>> > Ok, but in that case, you are not trying "distribution".... so really
>> don't
>> > understand.
>> > I though we were discussing the new fixed distribution that creates a
>> SDK
>> > in target folder or in the folder you specify (if use
>> > -DdistributionTargetFolder var)
>> > IOW, ant and maven continue to do the same as before, since there's no
>> > changes out side of distribution (just class paths set ups for maven
>> > generated artifacts that until now was empty or pointing to not existing
>> > resources)
>> >
>> >
>> > > No I don't have to and I shouldn't have to - I'm using artifacts from
>> > > Apache Maven Central.
>> > >
>> > >
>> > In that case you're not testing distribution. Jenkins builds the same as
>> > always. Other case will be if we can change Jenkins to build with
>> > distribution and then provide that SDK to download, that will be the
>> proper
>> > way, and what the rest of projects using maven does in fact.
>> >
>> >
>> >
>> >
>> > > --
>> > > Carlos Rovira
>> > > http://about.me/carlosrovira
>> > >
>> > >
>> > >
>> > >
>> >
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
before understand the mistake, I downloaded and tested SDK from Jenkins
(build #2552 that was the latest created) and build TDJ with VSCode and all
worked ok (the same output as with Maven distribution created locally)
Don't know if that report can be of help for you.
El mié., 22 ene. 2020 a las 13:22, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Exactly we are not discussion any stuff related to distribution :) We are
> discussion at some point that maybe for some reason your changes influence
> somehow compiler or anything else which end up with above error. Maybe that
> closure upgrade - I don't know. I look forward to hear more from someone
> what could know the reason of my issue.
>
> śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Piotr,
> >
> > El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > >
> > >
> > > Nope. Let's pretend that you have clean PC. You have downloaded your
> > Royale
> > > application which contains pom.xml - You do "mvn clean install" - All
> the
> > > dependencies will be downloaded from Apache Maven Central repository -
> > > which is being updated by every build ->
> > > https://builds.apache.org/job/Royale-asjs/ - Do you understand now
> what
> > > I'm
> > > using now ?
> > >
> > >
> > Ok, but in that case, you are not trying "distribution".... so really
> don't
> > understand.
> > I though we were discussing the new fixed distribution that creates a SDK
> > in target folder or in the folder you specify (if use
> > -DdistributionTargetFolder var)
> > IOW, ant and maven continue to do the same as before, since there's no
> > changes out side of distribution (just class paths set ups for maven
> > generated artifacts that until now was empty or pointing to not existing
> > resources)
> >
> >
> > > No I don't have to and I shouldn't have to - I'm using artifacts from
> > > Apache Maven Central.
> > >
> > >
> > In that case you're not testing distribution. Jenkins builds the same as
> > always. Other case will be if we can change Jenkins to build with
> > distribution and then provide that SDK to download, that will be the
> proper
> > way, and what the rest of projects using maven does in fact.
> >
> >
> >
> >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> > >
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Exactly we are not discussion any stuff related to distribution :) We are
discussion at some point that maybe for some reason your changes influence
somehow compiler or anything else which end up with above error. Maybe that
closure upgrade - I don't know. I look forward to hear more from someone
what could know the reason of my issue.
śr., 22 sty 2020 o 13:16 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Piotr,
>
> El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> >
> >
> > Nope. Let's pretend that you have clean PC. You have downloaded your
> Royale
> > application which contains pom.xml - You do "mvn clean install" - All the
> > dependencies will be downloaded from Apache Maven Central repository -
> > which is being updated by every build ->
> > https://builds.apache.org/job/Royale-asjs/ - Do you understand now what
> > I'm
> > using now ?
> >
> >
> Ok, but in that case, you are not trying "distribution".... so really don't
> understand.
> I though we were discussing the new fixed distribution that creates a SDK
> in target folder or in the folder you specify (if use
> -DdistributionTargetFolder var)
> IOW, ant and maven continue to do the same as before, since there's no
> changes out side of distribution (just class paths set ups for maven
> generated artifacts that until now was empty or pointing to not existing
> resources)
>
>
> > No I don't have to and I shouldn't have to - I'm using artifacts from
> > Apache Maven Central.
> >
> >
> In that case you're not testing distribution. Jenkins builds the same as
> always. Other case will be if we can change Jenkins to build with
> distribution and then provide that SDK to download, that will be the proper
> way, and what the rest of projects using maven does in fact.
>
>
>
>
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
> >
> >
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
>
>
> Nope. Let's pretend that you have clean PC. You have downloaded your Royale
> application which contains pom.xml - You do "mvn clean install" - All the
> dependencies will be downloaded from Apache Maven Central repository -
> which is being updated by every build ->
> https://builds.apache.org/job/Royale-asjs/ - Do you understand now what
> I'm
> using now ?
>
>
Ok, but in that case, you are not trying "distribution".... so really don't
understand.
I though we were discussing the new fixed distribution that creates a SDK
in target folder or in the folder you specify (if use
-DdistributionTargetFolder var)
IOW, ant and maven continue to do the same as before, since there's no
changes out side of distribution (just class paths set ups for maven
generated artifacts that until now was empty or pointing to not existing
resources)
> No I don't have to and I shouldn't have to - I'm using artifacts from
> Apache Maven Central.
>
>
In that case you're not testing distribution. Jenkins builds the same as
always. Other case will be if we can change Jenkins to build with
distribution and then provide that SDK to download, that will be the proper
way, and what the rest of projects using maven does in fact.
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
>
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Comments inline:
śr., 22 sty 2020 o 12:46 Carlos Rovira <ca...@apache.org> napisał(a):
> Yes, I tried, and worked from js_only links, but as I did, I recall that
> does not have any sense, since is the normal sdk Jenkins is building.
> So reset...since I think we are not understanding to each one :)
>
> Your first email talk about you building your project with maven. I suppose
> that you build distribution SDK right?
>
Nope. Let's pretend that you have clean PC. You have downloaded your Royale
application which contains pom.xml - You do "mvn clean install" - All the
dependencies will be downloaded from Apache Maven Central repository -
which is being updated by every build ->
https://builds.apache.org/job/Royale-asjs/ - Do you understand now what I'm
using now ?
> That didn't work, since the error was the one Josh stated yesterday to me
> privately (about having GOOG_HOME set) and I fixed around 12h by now.
>
> So to fix that...you must build maven distribution with latest fixes and
> feed your IDE with that distribution/SDK and report if you have some
> problems.
>
>
No I don't have to and I shouldn't have to - I'm using artifacts from
Apache Maven Central.
> From that point we can go on
>
> Thanks
>
>
> El mié., 22 ene. 2020 a las 12:37, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > You will try to download from which Jenkins? - Do you refer to ->
> > https://builds.apache.org/job/Royale-asjs/ or >
> >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > ?
> >
> > śr., 22 sty 2020 o 12:32 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > one thing I already said is that currently Maven distribution is SWF
> and
> > > JS, (not JS only). I requested Chris that I want to get JS only as
> well,
> > so
> > > I need him to guide me for this change. Anyway, distribution requires
> the
> > > profile "option-with-swf" to work (in other case it fails and inform
> > about
> > > that requirement)
> > >
> > > I'll try to download from Jenkins and see what happens, since I just
> > tested
> > > locally.
> > >
> > > Thanks
> > >
> > >
> > > El mié., 22 ene. 2020 a las 12:13, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > It is possible that Moonshine issue build which is based on
> > > >
> > > >
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > > > -
> > > > may be something different than I reported after build by Maven.
> > > >
> > > > śr., 22 sty 2020 o 12:03 Piotr Zarzycki <pi...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > Carlos,
> > > > >
> > > > > Just to make sure that you understand. When I'm building my
> > > application I
> > > > > don't relay on local build from sources - I only rely on what
> Jenkins
> > > is
> > > > > building. In case of Maven it would be
> > > > > https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it
> > > would
> > > > > be
> > > > >
> > > >
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > śr., 22 sty 2020 o 12:00 Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > > > > napisał(a):
> > > > >
> > > > >> In case of Maven I have used this ->
> > > > >> https://builds.apache.org/job/Royale-asjs/2551/ and that
> > > > >> https://builds.apache.org/job/Royale-compiler/1255/ - Those
> builds
> > > > >> should contains your changes.
> > > > >>
> > > > >> śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org>
> > > > >> napisał(a):
> > > > >>
> > > > >>> Hi Piotr,
> > > > >>>
> > > > >>> first I need to know about the other email I sent just now, if
> > you're
> > > > >>> using
> > > > >>> latest sources, and depending on that will go over this
> > > > >>>
> > > > >>>
> > > > >>> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
> > > > >>> piotrzarzycki21@gmail.com>) escribió:
> > > > >>>
> > > > >>> > Ok doing build trough Moonshine it's actually also failing. I
> did
> > > > build
> > > > >>> > with -debug=false and got following exception:
> > > > >>> >
> > > > >>> > : Internal error: java.nio.file.InvalidPathException: Illegal
> > char
> > > > <:>
> > > > >>> at
> > > > >>> > index 4:
> > > > >>> >
> > > > >>> >
> > > > >>>
> > > >
> > >
> >
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
> > > > >>> >
> > > > >>> >
> > > > >>>
> > > >
> > >
> >
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
> > > > >>> >
> > > > >>> > I'm not really sure if this is the problem with path of the
> file
> > or
> > > > >>> > something in the code. :/
> > > > >>> >
> > > > >>> > Thanks,
> > > > >>> > Piotr
> > > > >>> >
> > > > >>> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <
> > piotrzarzycki21@gmail.com
> > > >
> > > > >>> > napisał(a):
> > > > >>> >
> > > > >>> > > Hi Guys,
> > > > >>> > >
> > > > >>> > > I have just tired build our project with Maven (we are using
> it
> > > > when
> > > > >>> > > wanted to deploy version on the server) and I'm getting
> > following
> > > > >>> > > compilation error:
> > > > >>> > >
> > > > >>> > > got null for string/internal.js
> > > > >>> > >> got null for debug/errorcontext.js
> > > > >>> > >> got null for debug/debug.js
> > > > >>> > >> Internal error: java.lang.NullPointerException
> > > > >>> > >>
> > > > >>> >
> > > > >>>
> > > >
> > >
> >
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > > >>> > >>
> > > > >>> >
> > > > >>>
> > > >
> > >
> >
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> > > > >>> > >
> > > > >>> > >
> > > > >>> > > Anyone know what it could be ? I don't have such errors when
> > I'm
> > > > >>> building
> > > > >>> > > stuff using Moonshine. - I have used in that case following
> > > version
> > > > >>> of
> > > > >>> > > Nightly [1]
> > > > >>> > >
> > > > >>> > > [1]
> > > > >>> > >
> > > > >>> >
> > > > >>>
> > > >
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
> > > > >>> > >
> > > > >>> > > Thanks,
> > > > >>> > > --
> > > > >>> > >
> > > > >>> > > Piotr Zarzycki
> > > > >>> > >
> > > > >>> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >>> > > <https://www.patreon.com/piotrzarzycki>*
> > > > >>> > >
> > > > >>> >
> > > > >>> >
> > > > >>> > --
> > > > >>> >
> > > > >>> > Piotr Zarzycki
> > > > >>> >
> > > > >>> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >>> > <https://www.patreon.com/piotrzarzycki>*
> > > > >>> >
> > > > >>>
> > > > >>>
> > > > >>> --
> > > > >>> Carlos Rovira
> > > > >>> http://about.me/carlosrovira
> > > > >>>
> > > > >>
> > > > >>
> > > > >> --
> > > > >>
> > > > >> Piotr Zarzycki
> > > > >>
> > > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > > >> <https://www.patreon.com/piotrzarzycki>*
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Yes, I tried, and worked from js_only links, but as I did, I recall that
does not have any sense, since is the normal sdk Jenkins is building.
So reset...since I think we are not understanding to each one :)
Your first email talk about you building your project with maven. I suppose
that you build distribution SDK right?
That didn't work, since the error was the one Josh stated yesterday to me
privately (about having GOOG_HOME set) and I fixed around 12h by now.
So to fix that...you must build maven distribution with latest fixes and
feed your IDE with that distribution/SDK and report if you have some
problems.
From that point we can go on
Thanks
El mié., 22 ene. 2020 a las 12:37, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> You will try to download from which Jenkins? - Do you refer to ->
> https://builds.apache.org/job/Royale-asjs/ or >
>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> ?
>
> śr., 22 sty 2020 o 12:32 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Piotr,
> >
> > one thing I already said is that currently Maven distribution is SWF and
> > JS, (not JS only). I requested Chris that I want to get JS only as well,
> so
> > I need him to guide me for this change. Anyway, distribution requires the
> > profile "option-with-swf" to work (in other case it fails and inform
> about
> > that requirement)
> >
> > I'll try to download from Jenkins and see what happens, since I just
> tested
> > locally.
> >
> > Thanks
> >
> >
> > El mié., 22 ene. 2020 a las 12:13, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > It is possible that Moonshine issue build which is based on
> > >
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > > -
> > > may be something different than I reported after build by Maven.
> > >
> > > śr., 22 sty 2020 o 12:03 Piotr Zarzycki <pi...@gmail.com>
> > > napisał(a):
> > >
> > > > Carlos,
> > > >
> > > > Just to make sure that you understand. When I'm building my
> > application I
> > > > don't relay on local build from sources - I only rely on what Jenkins
> > is
> > > > building. In case of Maven it would be
> > > > https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it
> > would
> > > > be
> > > >
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > > >
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > śr., 22 sty 2020 o 12:00 Piotr Zarzycki <pi...@gmail.com>
> > > > napisał(a):
> > > >
> > > >> In case of Maven I have used this ->
> > > >> https://builds.apache.org/job/Royale-asjs/2551/ and that
> > > >> https://builds.apache.org/job/Royale-compiler/1255/ - Those builds
> > > >> should contains your changes.
> > > >>
> > > >> śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org>
> > > >> napisał(a):
> > > >>
> > > >>> Hi Piotr,
> > > >>>
> > > >>> first I need to know about the other email I sent just now, if
> you're
> > > >>> using
> > > >>> latest sources, and depending on that will go over this
> > > >>>
> > > >>>
> > > >>> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
> > > >>> piotrzarzycki21@gmail.com>) escribió:
> > > >>>
> > > >>> > Ok doing build trough Moonshine it's actually also failing. I did
> > > build
> > > >>> > with -debug=false and got following exception:
> > > >>> >
> > > >>> > : Internal error: java.nio.file.InvalidPathException: Illegal
> char
> > > <:>
> > > >>> at
> > > >>> > index 4:
> > > >>> >
> > > >>> >
> > > >>>
> > >
> >
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
> > > >>> >
> > > >>> >
> > > >>>
> > >
> >
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
> > > >>> >
> > > >>> > I'm not really sure if this is the problem with path of the file
> or
> > > >>> > something in the code. :/
> > > >>> >
> > > >>> > Thanks,
> > > >>> > Piotr
> > > >>> >
> > > >>> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <
> piotrzarzycki21@gmail.com
> > >
> > > >>> > napisał(a):
> > > >>> >
> > > >>> > > Hi Guys,
> > > >>> > >
> > > >>> > > I have just tired build our project with Maven (we are using it
> > > when
> > > >>> > > wanted to deploy version on the server) and I'm getting
> following
> > > >>> > > compilation error:
> > > >>> > >
> > > >>> > > got null for string/internal.js
> > > >>> > >> got null for debug/errorcontext.js
> > > >>> > >> got null for debug/debug.js
> > > >>> > >> Internal error: java.lang.NullPointerException
> > > >>> > >>
> > > >>> >
> > > >>>
> > >
> >
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > >>> > >>
> > > >>> >
> > > >>>
> > >
> >
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> > > >>> > >
> > > >>> > >
> > > >>> > > Anyone know what it could be ? I don't have such errors when
> I'm
> > > >>> building
> > > >>> > > stuff using Moonshine. - I have used in that case following
> > version
> > > >>> of
> > > >>> > > Nightly [1]
> > > >>> > >
> > > >>> > > [1]
> > > >>> > >
> > > >>> >
> > > >>>
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
> > > >>> > >
> > > >>> > > Thanks,
> > > >>> > > --
> > > >>> > >
> > > >>> > > Piotr Zarzycki
> > > >>> > >
> > > >>> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > >>> > > <https://www.patreon.com/piotrzarzycki>*
> > > >>> > >
> > > >>> >
> > > >>> >
> > > >>> > --
> > > >>> >
> > > >>> > Piotr Zarzycki
> > > >>> >
> > > >>> > Patreon: *https://www.patreon.com/piotrzarzycki
> > > >>> > <https://www.patreon.com/piotrzarzycki>*
> > > >>> >
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Carlos Rovira
> > > >>> http://about.me/carlosrovira
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >> Piotr Zarzycki
> > > >>
> > > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > > >> <https://www.patreon.com/piotrzarzycki>*
> > > >>
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
You will try to download from which Jenkins? - Do you refer to ->
https://builds.apache.org/job/Royale-asjs/ or >
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
?
śr., 22 sty 2020 o 12:32 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Piotr,
>
> one thing I already said is that currently Maven distribution is SWF and
> JS, (not JS only). I requested Chris that I want to get JS only as well, so
> I need him to guide me for this change. Anyway, distribution requires the
> profile "option-with-swf" to work (in other case it fails and inform about
> that requirement)
>
> I'll try to download from Jenkins and see what happens, since I just tested
> locally.
>
> Thanks
>
>
> El mié., 22 ene. 2020 a las 12:13, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > It is possible that Moonshine issue build which is based on
> >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > -
> > may be something different than I reported after build by Maven.
> >
> > śr., 22 sty 2020 o 12:03 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> > > Carlos,
> > >
> > > Just to make sure that you understand. When I'm building my
> application I
> > > don't relay on local build from sources - I only rely on what Jenkins
> is
> > > building. In case of Maven it would be
> > > https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it
> would
> > > be
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > >
> > >
> > > Thanks,
> > > Piotr
> > >
> > > śr., 22 sty 2020 o 12:00 Piotr Zarzycki <pi...@gmail.com>
> > > napisał(a):
> > >
> > >> In case of Maven I have used this ->
> > >> https://builds.apache.org/job/Royale-asjs/2551/ and that
> > >> https://builds.apache.org/job/Royale-compiler/1255/ - Those builds
> > >> should contains your changes.
> > >>
> > >> śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org>
> > >> napisał(a):
> > >>
> > >>> Hi Piotr,
> > >>>
> > >>> first I need to know about the other email I sent just now, if you're
> > >>> using
> > >>> latest sources, and depending on that will go over this
> > >>>
> > >>>
> > >>> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
> > >>> piotrzarzycki21@gmail.com>) escribió:
> > >>>
> > >>> > Ok doing build trough Moonshine it's actually also failing. I did
> > build
> > >>> > with -debug=false and got following exception:
> > >>> >
> > >>> > : Internal error: java.nio.file.InvalidPathException: Illegal char
> > <:>
> > >>> at
> > >>> > index 4:
> > >>> >
> > >>> >
> > >>>
> >
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
> > >>> >
> > >>> >
> > >>>
> >
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
> > >>> >
> > >>> > I'm not really sure if this is the problem with path of the file or
> > >>> > something in the code. :/
> > >>> >
> > >>> > Thanks,
> > >>> > Piotr
> > >>> >
> > >>> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > >>> > napisał(a):
> > >>> >
> > >>> > > Hi Guys,
> > >>> > >
> > >>> > > I have just tired build our project with Maven (we are using it
> > when
> > >>> > > wanted to deploy version on the server) and I'm getting following
> > >>> > > compilation error:
> > >>> > >
> > >>> > > got null for string/internal.js
> > >>> > >> got null for debug/errorcontext.js
> > >>> > >> got null for debug/debug.js
> > >>> > >> Internal error: java.lang.NullPointerException
> > >>> > >>
> > >>> >
> > >>>
> >
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > >>> > >>
> > >>> >
> > >>>
> >
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> > >>> > >
> > >>> > >
> > >>> > > Anyone know what it could be ? I don't have such errors when I'm
> > >>> building
> > >>> > > stuff using Moonshine. - I have used in that case following
> version
> > >>> of
> > >>> > > Nightly [1]
> > >>> > >
> > >>> > > [1]
> > >>> > >
> > >>> >
> > >>>
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
> > >>> > >
> > >>> > > Thanks,
> > >>> > > --
> > >>> > >
> > >>> > > Piotr Zarzycki
> > >>> > >
> > >>> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > >>> > > <https://www.patreon.com/piotrzarzycki>*
> > >>> > >
> > >>> >
> > >>> >
> > >>> > --
> > >>> >
> > >>> > Piotr Zarzycki
> > >>> >
> > >>> > Patreon: *https://www.patreon.com/piotrzarzycki
> > >>> > <https://www.patreon.com/piotrzarzycki>*
> > >>> >
> > >>>
> > >>>
> > >>> --
> > >>> Carlos Rovira
> > >>> http://about.me/carlosrovira
> > >>>
> > >>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> <https://www.patreon.com/piotrzarzycki>*
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
My problem is completely unrelated to distribution - unless your changes
influence other part. - I don't use Maven distribution to build anything.
śr., 22 sty 2020 o 12:32 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Piotr,
>
> one thing I already said is that currently Maven distribution is SWF and
> JS, (not JS only). I requested Chris that I want to get JS only as well, so
> I need him to guide me for this change. Anyway, distribution requires the
> profile "option-with-swf" to work (in other case it fails and inform about
> that requirement)
>
> I'll try to download from Jenkins and see what happens, since I just tested
> locally.
>
> Thanks
>
>
> El mié., 22 ene. 2020 a las 12:13, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > It is possible that Moonshine issue build which is based on
> >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > -
> > may be something different than I reported after build by Maven.
> >
> > śr., 22 sty 2020 o 12:03 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> > > Carlos,
> > >
> > > Just to make sure that you understand. When I'm building my
> application I
> > > don't relay on local build from sources - I only rely on what Jenkins
> is
> > > building. In case of Maven it would be
> > > https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it
> would
> > > be
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> > >
> > >
> > > Thanks,
> > > Piotr
> > >
> > > śr., 22 sty 2020 o 12:00 Piotr Zarzycki <pi...@gmail.com>
> > > napisał(a):
> > >
> > >> In case of Maven I have used this ->
> > >> https://builds.apache.org/job/Royale-asjs/2551/ and that
> > >> https://builds.apache.org/job/Royale-compiler/1255/ - Those builds
> > >> should contains your changes.
> > >>
> > >> śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org>
> > >> napisał(a):
> > >>
> > >>> Hi Piotr,
> > >>>
> > >>> first I need to know about the other email I sent just now, if you're
> > >>> using
> > >>> latest sources, and depending on that will go over this
> > >>>
> > >>>
> > >>> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
> > >>> piotrzarzycki21@gmail.com>) escribió:
> > >>>
> > >>> > Ok doing build trough Moonshine it's actually also failing. I did
> > build
> > >>> > with -debug=false and got following exception:
> > >>> >
> > >>> > : Internal error: java.nio.file.InvalidPathException: Illegal char
> > <:>
> > >>> at
> > >>> > index 4:
> > >>> >
> > >>> >
> > >>>
> >
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
> > >>> >
> > >>> >
> > >>>
> >
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
> > >>> >
> > >>> > I'm not really sure if this is the problem with path of the file or
> > >>> > something in the code. :/
> > >>> >
> > >>> > Thanks,
> > >>> > Piotr
> > >>> >
> > >>> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > >>> > napisał(a):
> > >>> >
> > >>> > > Hi Guys,
> > >>> > >
> > >>> > > I have just tired build our project with Maven (we are using it
> > when
> > >>> > > wanted to deploy version on the server) and I'm getting following
> > >>> > > compilation error:
> > >>> > >
> > >>> > > got null for string/internal.js
> > >>> > >> got null for debug/errorcontext.js
> > >>> > >> got null for debug/debug.js
> > >>> > >> Internal error: java.lang.NullPointerException
> > >>> > >>
> > >>> >
> > >>>
> >
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > >>> > >>
> > >>> >
> > >>>
> >
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> > >>> > >
> > >>> > >
> > >>> > > Anyone know what it could be ? I don't have such errors when I'm
> > >>> building
> > >>> > > stuff using Moonshine. - I have used in that case following
> version
> > >>> of
> > >>> > > Nightly [1]
> > >>> > >
> > >>> > > [1]
> > >>> > >
> > >>> >
> > >>>
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
> > >>> > >
> > >>> > > Thanks,
> > >>> > > --
> > >>> > >
> > >>> > > Piotr Zarzycki
> > >>> > >
> > >>> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > >>> > > <https://www.patreon.com/piotrzarzycki>*
> > >>> > >
> > >>> >
> > >>> >
> > >>> > --
> > >>> >
> > >>> > Piotr Zarzycki
> > >>> >
> > >>> > Patreon: *https://www.patreon.com/piotrzarzycki
> > >>> > <https://www.patreon.com/piotrzarzycki>*
> > >>> >
> > >>>
> > >>>
> > >>> --
> > >>> Carlos Rovira
> > >>> http://about.me/carlosrovira
> > >>>
> > >>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> <https://www.patreon.com/piotrzarzycki>*
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
one thing I already said is that currently Maven distribution is SWF and
JS, (not JS only). I requested Chris that I want to get JS only as well, so
I need him to guide me for this change. Anyway, distribution requires the
profile "option-with-swf" to work (in other case it fails and inform about
that requirement)
I'll try to download from Jenkins and see what happens, since I just tested
locally.
Thanks
El mié., 22 ene. 2020 a las 12:13, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> It is possible that Moonshine issue build which is based on
>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> -
> may be something different than I reported after build by Maven.
>
> śr., 22 sty 2020 o 12:03 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Carlos,
> >
> > Just to make sure that you understand. When I'm building my application I
> > don't relay on local build from sources - I only rely on what Jenkins is
> > building. In case of Maven it would be
> > https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it would
> > be
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
> >
> >
> > Thanks,
> > Piotr
> >
> > śr., 22 sty 2020 o 12:00 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> >> In case of Maven I have used this ->
> >> https://builds.apache.org/job/Royale-asjs/2551/ and that
> >> https://builds.apache.org/job/Royale-compiler/1255/ - Those builds
> >> should contains your changes.
> >>
> >> śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org>
> >> napisał(a):
> >>
> >>> Hi Piotr,
> >>>
> >>> first I need to know about the other email I sent just now, if you're
> >>> using
> >>> latest sources, and depending on that will go over this
> >>>
> >>>
> >>> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
> >>> piotrzarzycki21@gmail.com>) escribió:
> >>>
> >>> > Ok doing build trough Moonshine it's actually also failing. I did
> build
> >>> > with -debug=false and got following exception:
> >>> >
> >>> > : Internal error: java.nio.file.InvalidPathException: Illegal char
> <:>
> >>> at
> >>> > index 4:
> >>> >
> >>> >
> >>>
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
> >>> >
> >>> >
> >>>
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
> >>> >
> >>> > I'm not really sure if this is the problem with path of the file or
> >>> > something in the code. :/
> >>> >
> >>> > Thanks,
> >>> > Piotr
> >>> >
> >>> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <pi...@gmail.com>
> >>> > napisał(a):
> >>> >
> >>> > > Hi Guys,
> >>> > >
> >>> > > I have just tired build our project with Maven (we are using it
> when
> >>> > > wanted to deploy version on the server) and I'm getting following
> >>> > > compilation error:
> >>> > >
> >>> > > got null for string/internal.js
> >>> > >> got null for debug/errorcontext.js
> >>> > >> got null for debug/debug.js
> >>> > >> Internal error: java.lang.NullPointerException
> >>> > >>
> >>> >
> >>>
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>> > >>
> >>> >
> >>>
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> >>> > >
> >>> > >
> >>> > > Anyone know what it could be ? I don't have such errors when I'm
> >>> building
> >>> > > stuff using Moonshine. - I have used in that case following version
> >>> of
> >>> > > Nightly [1]
> >>> > >
> >>> > > [1]
> >>> > >
> >>> >
> >>>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
> >>> > >
> >>> > > Thanks,
> >>> > > --
> >>> > >
> >>> > > Piotr Zarzycki
> >>> > >
> >>> > > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > > <https://www.patreon.com/piotrzarzycki>*
> >>> > >
> >>> >
> >>> >
> >>> > --
> >>> >
> >>> > Piotr Zarzycki
> >>> >
> >>> > Patreon: *https://www.patreon.com/piotrzarzycki
> >>> > <https://www.patreon.com/piotrzarzycki>*
> >>> >
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
It is possible that Moonshine issue build which is based on
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
-
may be something different than I reported after build by Maven.
śr., 22 sty 2020 o 12:03 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Carlos,
>
> Just to make sure that you understand. When I'm building my application I
> don't relay on local build from sources - I only rely on what Jenkins is
> building. In case of Maven it would be
> https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it would
> be
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
>
>
> Thanks,
> Piotr
>
> śr., 22 sty 2020 o 12:00 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> In case of Maven I have used this ->
>> https://builds.apache.org/job/Royale-asjs/2551/ and that
>> https://builds.apache.org/job/Royale-compiler/1255/ - Those builds
>> should contains your changes.
>>
>> śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org>
>> napisał(a):
>>
>>> Hi Piotr,
>>>
>>> first I need to know about the other email I sent just now, if you're
>>> using
>>> latest sources, and depending on that will go over this
>>>
>>>
>>> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
>>> piotrzarzycki21@gmail.com>) escribió:
>>>
>>> > Ok doing build trough Moonshine it's actually also failing. I did build
>>> > with -debug=false and got following exception:
>>> >
>>> > : Internal error: java.nio.file.InvalidPathException: Illegal char <:>
>>> at
>>> > index 4:
>>> >
>>> >
>>> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
>>> >
>>> >
>>> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
>>> >
>>> > I'm not really sure if this is the problem with path of the file or
>>> > something in the code. :/
>>> >
>>> > Thanks,
>>> > Piotr
>>> >
>>> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <pi...@gmail.com>
>>> > napisał(a):
>>> >
>>> > > Hi Guys,
>>> > >
>>> > > I have just tired build our project with Maven (we are using it when
>>> > > wanted to deploy version on the server) and I'm getting following
>>> > > compilation error:
>>> > >
>>> > > got null for string/internal.js
>>> > >> got null for debug/errorcontext.js
>>> > >> got null for debug/debug.js
>>> > >> Internal error: java.lang.NullPointerException
>>> > >>
>>> >
>>> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> > >>
>>> >
>>> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>> > >
>>> > >
>>> > > Anyone know what it could be ? I don't have such errors when I'm
>>> building
>>> > > stuff using Moonshine. - I have used in that case following version
>>> of
>>> > > Nightly [1]
>>> > >
>>> > > [1]
>>> > >
>>> >
>>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
>>> > >
>>> > > Thanks,
>>> > > --
>>> > >
>>> > > Piotr Zarzycki
>>> > >
>>> > > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > <https://www.patreon.com/piotrzarzycki>*
>>> > >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > <https://www.patreon.com/piotrzarzycki>*
>>> >
>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Carlos,
Just to make sure that you understand. When I'm building my application I
don't relay on local build from sources - I only rely on what Jenkins is
building. In case of Maven it would be
https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it would be
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
Thanks,
Piotr
śr., 22 sty 2020 o 12:00 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> In case of Maven I have used this ->
> https://builds.apache.org/job/Royale-asjs/2551/ and that
> https://builds.apache.org/job/Royale-compiler/1255/ - Those builds should
> contains your changes.
>
> śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Hi Piotr,
>>
>> first I need to know about the other email I sent just now, if you're
>> using
>> latest sources, and depending on that will go over this
>>
>>
>> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
>> piotrzarzycki21@gmail.com>) escribió:
>>
>> > Ok doing build trough Moonshine it's actually also failing. I did build
>> > with -debug=false and got following exception:
>> >
>> > : Internal error: java.nio.file.InvalidPathException: Illegal char <:>
>> at
>> > index 4:
>> >
>> >
>> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
>> >
>> >
>> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
>> >
>> > I'm not really sure if this is the problem with path of the file or
>> > something in the code. :/
>> >
>> > Thanks,
>> > Piotr
>> >
>> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <pi...@gmail.com>
>> > napisał(a):
>> >
>> > > Hi Guys,
>> > >
>> > > I have just tired build our project with Maven (we are using it when
>> > > wanted to deploy version on the server) and I'm getting following
>> > > compilation error:
>> > >
>> > > got null for string/internal.js
>> > >> got null for debug/errorcontext.js
>> > >> got null for debug/debug.js
>> > >> Internal error: java.lang.NullPointerException
>> > >>
>> >
>> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> > >>
>> >
>> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> > >
>> > >
>> > > Anyone know what it could be ? I don't have such errors when I'm
>> building
>> > > stuff using Moonshine. - I have used in that case following version of
>> > > Nightly [1]
>> > >
>> > > [1]
>> > >
>> >
>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
>> > >
>> > > Thanks,
>> > > --
>> > >
>> > > Piotr Zarzycki
>> > >
>> > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > <https://www.patreon.com/piotrzarzycki>*
>> > >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > <https://www.patreon.com/piotrzarzycki>*
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
In case of Maven I have used this ->
https://builds.apache.org/job/Royale-asjs/2551/ and that
https://builds.apache.org/job/Royale-compiler/1255/ - Those builds should
contains your changes.
śr., 22 sty 2020 o 11:58 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Piotr,
>
> first I need to know about the other email I sent just now, if you're using
> latest sources, and depending on that will go over this
>
>
> El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Ok doing build trough Moonshine it's actually also failing. I did build
> > with -debug=false and got following exception:
> >
> > : Internal error: java.nio.file.InvalidPathException: Illegal char <:> at
> > index 4:
> >
> >
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
> >
> >
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
> >
> > I'm not really sure if this is the problem with path of the file or
> > something in the code. :/
> >
> > Thanks,
> > Piotr
> >
> > śr., 22 sty 2020 o 10:19 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> > > Hi Guys,
> > >
> > > I have just tired build our project with Maven (we are using it when
> > > wanted to deploy version on the server) and I'm getting following
> > > compilation error:
> > >
> > > got null for string/internal.js
> > >> got null for debug/errorcontext.js
> > >> got null for debug/debug.js
> > >> Internal error: java.lang.NullPointerException
> > >>
> >
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > >>
> >
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> > >
> > >
> > > Anyone know what it could be ? I don't have such errors when I'm
> building
> > > stuff using Moonshine. - I have used in that case following version of
> > > Nightly [1]
> > >
> > > [1]
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
> > >
> > > Thanks,
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
first I need to know about the other email I sent just now, if you're using
latest sources, and depending on that will go over this
El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Ok doing build trough Moonshine it's actually also failing. I did build
> with -debug=false and got following exception:
>
> : Internal error: java.nio.file.InvalidPathException: Illegal char <:> at
> index 4:
>
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
>
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
>
> I'm not really sure if this is the problem with path of the file or
> something in the code. :/
>
> Thanks,
> Piotr
>
> śr., 22 sty 2020 o 10:19 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Hi Guys,
> >
> > I have just tired build our project with Maven (we are using it when
> > wanted to deploy version on the server) and I'm getting following
> > compilation error:
> >
> > got null for string/internal.js
> >> got null for debug/errorcontext.js
> >> got null for debug/debug.js
> >> Internal error: java.lang.NullPointerException
> >>
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> >
> >
> > Anyone know what it could be ? I don't have such errors when I'm building
> > stuff using Moonshine. - I have used in that case following version of
> > Nightly [1]
> >
> > [1]
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
I have used the oldest available build [1] and it's still failing when I'm
building trough Moonshine.
[1]
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/656/
śr., 22 sty 2020 o 10:40 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Ok doing build trough Moonshine it's actually also failing. I did build
> with -debug=false and got following exception:
>
> : Internal error: java.nio.file.InvalidPathException: Illegal char <:> at
> index 4:
> file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
> sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
>
> I'm not really sure if this is the problem with path of the file or
> something in the code. :/
>
> Thanks,
> Piotr
>
> śr., 22 sty 2020 o 10:19 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> Hi Guys,
>>
>> I have just tired build our project with Maven (we are using it when
>> wanted to deploy version on the server) and I'm getting following
>> compilation error:
>>
>> got null for string/internal.js
>>> got null for debug/errorcontext.js
>>> got null for debug/debug.js
>>> Internal error: java.lang.NullPointerException
>>> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>>
>> Anyone know what it could be ? I don't have such errors when I'm building
>> stuff using Moonshine. - I have used in that case following version of
>> Nightly [1]
>>
>> [1]
>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
>>
>> Thanks,
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Ok doing build trough Moonshine it's actually also failing. I did build
with -debug=false and got following exception:
: Internal error: java.nio.file.InvalidPathException: Illegal char <:> at
index 4:
file:///THIS_WAS_FULL_PATH_BUT_I_HAD_TO_DELETE_DUE_TO_confidentiality_src/net/prominic/utils/UtilsCore.as
sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)sun.nio.fs.AbstractPath.resolveSibling(AbstractPath.java:66)com.google.javascript.jscomp.SourceMapResolver.getRelativePath(SourceMapResolver.java:102)com.google.javascript.jscomp.Compiler.getSourceMapping(Compiler.java:2898)com.google.javascript.jscomp.LightweightMessageFormatter.format(LightweightMessageFormatter.java:95)com.google.javascript.jscomp.LightweightMessageFormatter.formatError(LightweightMessageFormatter.java:74)com.google.javascript.jscomp.JSError.format(JSError.java:163)com.google.javascript.jscomp.LoggerErrorManager.println(LoggerErrorManager.java:53)com.google.javascript.jscomp.BasicErrorManager.generateReport(BasicErrorManager.java:39)com.google.javascript.jscomp.ThreadSafeDelegatingErrorManager.generateReport(ThreadSafeDelegatingErrorManager.java:39)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:766)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)
I'm not really sure if this is the problem with path of the file or
something in the code. :/
Thanks,
Piotr
śr., 22 sty 2020 o 10:19 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Guys,
>
> I have just tired build our project with Maven (we are using it when
> wanted to deploy version on the server) and I'm getting following
> compilation error:
>
> got null for string/internal.js
>> got null for debug/errorcontext.js
>> got null for debug/debug.js
>> Internal error: java.lang.NullPointerException
>> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
>
> Anyone know what it could be ? I don't have such errors when I'm building
> stuff using Moonshine. - I have used in that case following version of
> Nightly [1]
>
> [1]
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Building Royale project with Maven throws NPE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
this error was the issue yesterday without the GOOG_HOME patch.
did you rebuild today with latest fixes in compiler and framework?
El mié., 22 ene. 2020 a las 10:19, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Hi Guys,
>
> I have just tired build our project with Maven (we are using it when wanted
> to deploy version on the server) and I'm getting following compilation
> error:
>
> got null for string/internal.js
> > got null for debug/errorcontext.js
> > got null for debug/debug.js
> > Internal error: java.lang.NullPointerException
> >
> com.google.javascript.jscomp.Compiler.newTracer(Compiler.java:1256)com.google.javascript.jscomp.Compiler.generateReport(Compiler.java:765)com.google.javascript.jscomp.Compiler.compile(Compiler.java:751)org.apache.royale.compiler.utils.JSClosureCompilerWrapper.compile(JSClosureCompilerWrapper.java:164)org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java:568)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:441)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:234)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:375)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)org.apache.maven.cli.MavenCli.main(MavenCli.java:192)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >
> Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:498)org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
>
> Anyone know what it could be ? I don't have such errors when I'm building
> stuff using Moonshine. - I have used in that case following version of
> Nightly [1]
>
> [1]
>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/665/
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira