Great to know! Thanks!
czw., 23 sty 2020 o 18:41 Alex Harui 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" wrote:
>
> Hi Alex,
>
> I do have
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" wrote:
Hi Alex,
I do have other project which is using PureMVC - I could compare with that.
Anyway it is
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
Right, I know it
El jue., 23 ene. 2020 a las 16:59, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> CRLF problem and build issue with ant distribution are two separate issues.
>
> czw., 23 sty 2020 o 16:39 Carlos Rovira
> napisał(a):
>
> > Hi,
> >
> > about maven distribution sdk I
CRLF problem and build issue with ant distribution are two separate issues.
czw., 23 sty 2020 o 16:39 Carlos Rovira
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
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 (<
piotrzarzyck...@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]
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 (<
piotrzarzyck...@gmail.com>) escribió:
> Maven build for our application back to normal and I
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
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
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" wrote:
It looks like I have two separate issues - apart of behavior
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:
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 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
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 ()
escribió:
> Hi Piotr,
>
> I can see the problem is related to my latest commit in compiler to solve
> the GOOG_HOME problem.
>
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 ()
escribió:
> Hi Piotr,
>
> ok, now I understand... It's clear that I broke something since trying to
> build now with
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
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
Testing distribution is being handled in separate thread - you are mixing
subjects :)
śr., 22 sty 2020 o 13:22 Piotr Zarzycki
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
>
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
Hi Piotr,
El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (<
piotrzarzyck...@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
Comments inline:
śr., 22 sty 2020 o 12:46 Carlos Rovira 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
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
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 napisał(a):
> Hi Piotr,
>
> one thing I already said is that
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 napisał(a):
> Hi Piotr,
>
> one thing I already said is that currently Maven distribution is SWF and
> JS,
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
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
napisał(a):
> Carlos,
>
> Just to make sure that
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
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 napisał(a):
> Hi Piotr,
>
> first I need to know about the other
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 (<
piotrzarzyck...@gmail.com>) escribió:
> Ok doing build trough Moonshine it's actually also failing.
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 (<
piotrzarzyck...@gmail.com>) escribió:
> Hi Guys,
>
> I have just tired build our project with Maven
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
napisał(a):
> Ok doing build trough Moonshine it's actually also
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:
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:
32 matches
Mail list logo