ViewSlowDealerEventLayout.mxml"
URL: https://cloud.dallmeier.com/index.php/s/DBWQRZTNkb7rexm
Password: ~x+4!m%DvAe9
There is no generated file for "ASADetailViewHeaderStatisticEventsDefault.as"
Error for reference again:
[compc] D:\Program Files
(x86)\Jenkins\workspace\SeMS
new debug branch from the very
same older revision where the issue did occur and I was able to reproduce it
with the same error.
However, when I add "keep-generated-actionscript="true"" to compc compiler
options no build error occurs (I can find the code in the &quo
ion where the issue did occur and I was able to reproduce it
with the same error.
However, when I add "keep-generated-actionscript="true"" to compc compiler
options no build error occurs (I can find the code in the "generated" folder on
the CI).
Removing "
rking build (using directoy "SeMSy5-Translation-Tool", the
error has actually moved from "ASADVHStatisticEventsDefault" to the MXML file
"ASADetailViewSlowDealerEventLayout".
[compc] D:\Program Files
(x86)\Jenkins\workspace\SeMSy5-Translation-Tool\SeMSy-Next-Lib\src\com
Jenkins checks out to and
builds).
Also, there are no other files called "ASADVHStatisticEventsDefault".
On the current not-working build (using directoy "SeMSy5-Translation-Tool", the
error has actually moved from "ASADVHStatisticEventsDefault" to the MXML fi
the @temp and @script folders (e.g.
SeMSy5-Translation-Tool@script), which Jenkins uses for checkout, were entirely
deleted]
[compc] D:\Program Files
(x86)\Jenkins\workspace\SeMSy5-Translation-Tool\SeMSy-Next-Lib\src\components\asaEvents\detailview\layout\ASADetailViewS
Translation-Tool" was delete beforehand).
[Worth mentioning here that also the @temp and @script folders (e.g.
SeMSy5-Translation-Tool@script), which Jenkins uses for checkout, were entirely
deleted]
[compc] D:\Program Files
(x86)\Jenkins\workspace\SeMSy5-Translati
##- Please type your reply above this line -##
Your request (#464846) has been updated. To add additional comments, reply to
this email or click the link below:
--
Billie Abrahams, Oct 24, 2023, 23:54 GMT+3
Hello,
I don't see anything that points t
##- Please type your reply above this line -##
Your request (#464846) has been updated. To add additional comments, reply to
this email or click the link below:
--
Aaron McKane, Oct 24, 2023, 13:57 GMT+3
Hello,
Please specify the following informat
Hi Jan,
I downloaded the output and displayed it in VSCode. VSCode says there are 4808
lines of output.
It looks like compc is called several times, but the last call is on line 587.
On line 1747 the first of 3 errors are reported. I think that should cause the
build to fail.
One thing you
gistry Court:
Thomas Dallmeier
Amtsgericht Regensburg HRA 6827
DE813790649
Dallmeier GmbH
Amtsgericht Regensburg HRB 9085
-Ursprüngliche Nachricht-
Von: Alex Harui
Gesendet: Donnerstag, 19. Oktober 2023 19:14
An: users@flex.apache.org
Cc: Fischer Micha
till fails
to build. I did compare the entire contents of both folders with a diff ("Tool"
and "Tool2") and both are exactly the same.
The job/pipeline uses both, compc and mxmlc, to first build some libraries
using compc and then build the main executable using mxmlc.
Wh
too.
I deleted the entire folder for "Tool" so it gets recreated but it still fails
to build. I did compare the entire contents of both folders with a diff ("Tool"
and "Tool2") and both are exactly the same.
The job/pipeline uses both, compc and mxmlc, to first bu
Is there a valid job/workspace/pipeline that uses the folder ending in "Tool"
instead of "Tool2"? Otherwise, try deleting that workspace and see if it gets
re-created again and which job did it.
Are there other jobs or pipelines that run compc or mxmlc?
-Alex
On 10/9/
I’m reaching out to you regarding a rather strange behavior of compc on the
CI/Jenkins, when it tries to build a specific swc module within a pipeline
script.
An error occurs, where it looks like this is actually depending on the name of
the root folder where the modules are located at.
The
I don't think I've heard this exact case before, but IMO, incremental mode
is known to be flaky.
On 9/15/14 4:13 PM, "Subscriptions" wrote:
>Hi All,
>
>I've been having some issues compiling SWCs...
>
>When i run compc with incremental=false, everything
Hi All,
I've been having some issues compiling SWCs...
When i run compc with incremental=false, everything works. But if
incremental=true, none of the embedded assets are included.
Assets are embedded in .as file like so:
[Embed(source="/path/to/image.png")]
publ
_
Von: Raj U. Shaikh
Gesendet: Sonntag, 27. April 2014 14:29
An: users@flex.apache.org
Betreff: RE: compc additional compiler arguments
Hi Chris,
Please find attached library project depicting additional compiler arguments
using "-define=CONFIG::Version"
I consider there is no way to define
venting us from registering new users on the
Fllexmojos Jira :-(
Chris
-Ursprüngliche Nachricht-
Von: Raj U. Shaikh [mailto:raj.sha...@mastek.com]
Gesendet: Freitag, 11. April 2014 08:18
An: users@flex.apache.org
Betreff: RE: compc additional compiler arguments
I am using flexmojos and
ven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
I believe down the line it uses compc
e.org"
Betreff: compc additional compiler arguments
Datum: Do., Apr. 10, 2014 08:53
I dont use maven so i cant answer that
On 10/04/2014 15:40, Raj U. Shaikh wrote:
> Can I able to add this in pom xml(maven)? I searched on it but no clues..
>
> -Original Message-
> From
@flex.apache.org
Subject: Re: compc additional compiler arguments
Ignore my previous email with docs link ;(
You can add custom arguments to config files like so:
NAMESPACE::variable
your-value
On 10/04/2014 14:20, Raj U. Shaikh wrote:
Virat,
I am
Can I able to add this in pom xml(maven)? I searched on it but no clues..
-Original Message-
From: Lee Burrows [mailto:subscripti...@leeburrows.com]
Sent: Thursday, April 10, 2014 7:14 PM
To: users@flex.apache.org
Subject: Re: compc additional compiler arguments
Ignore my previous email
,
Raj Shaikh
-Original Message-
From: Patil, Virat [mailto:virat.pa...@capgemini.com]
Sent: Thursday, April 10, 2014 5:21 PM
To: users@flex.apache.org
Cc: Yogesh C. Jadhav
Subject: RE: compc additional compiler arguments
Hi Raj
Check out if this solves your problem. By passing Configuration
This is available in compc. see
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7a92.html
On 10/04/2014 14:20, Raj U. Shaikh wrote:
Hi All,
In mxmlc we have an option to define additional compiler arguments in following
way
-define=NAMESPACE::variable,value
But
Virat,
I am looking for custom arguments and not the predefined ones.
Regards,
Raj Shaikh
-Original Message-
From: Patil, Virat [mailto:virat.pa...@capgemini.com]
Sent: Thursday, April 10, 2014 5:21 PM
To: users@flex.apache.org
Cc: Yogesh C. Jadhav
Subject: RE: compc additional
compiler (compc) and either pass command-line arguments to
the compiler or pass a configuration XML file as the load-config argument.
Discussion
To invoke the Component compiler, compc, use this syntax:
compc -source-path . -include-classes oreilly.cookbook.foo -output example.swc
Some of the most
Hi All,
In mxmlc we have an option to define additional compiler arguments in following
way
-define=NAMESPACE::variable,value
But same is not available in compc. Is there have any alternate way for same?
I am creating a library project(swc) and want to set one argument/property to
it at
builds and processing,
I was able to find grunt-mxmlc plugin which worked quite nicely but cannot
find any grunt plugin for using compc compiler to create swc libraries...
So I thought to find out if any of you had any experience with this sort of
brew?
Cheers
Ajar
<http://www.casaversa.com
29 matches
Mail list logo
