We are looking through the code and see if we can figure out the
problem, we found couple warnings in the output and those two warnings
happen to be from the ones with the wrong swf names. Do you think you
can elaborate on what these 2 warnings mean? Also do you think you can
give us a starting point where we can look in the code? Like which
file is the one that build out the '-runtime-shared-library-path'
option?
tks.

[INFO] [flex-compiler-mojo:compile-swf {execution: default}]
[INFO] Flex-mojos 2.0.3 - GNU GPL License (NO WARRANTY) - See
COPYRIGHT file
[WARNING] Source file was not defined, flex-mojos will guess one.
[INFO] Using configuration file C:\workspace\kwong_iip_party_1_0_0_intg
\iip_part
y\party-flex-ui\target\classes\config.xml
[WARNING] Attempting to build MavenProject instance for Artifact
(com.fiserv.isd
.iip.uicore:iip-uicore-framework:RELEASE) of type: swc; constructing
POM artifac
t instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(com.fiserv.isd
.iip.uicore:iip-uicore-common:RELEASE) of type: swc; constructing POM
artifact i
nstead.
[INFO] Flex compiler configurations:
-compiler.accessible=false


On Jun 8, 11:40 am, Marvin Froeder <[email protected]> wrote:
> On Mon, Jun 8, 2009 at 2:34 PM, Ken <[email protected]> wrote:
> > What can I do to make it work?
>
> Honestly I have no idea.... (Didn't even knew that was possible)
>
> Maven is the one who resolve the dependencies, so I have idea why it didn't
> resolve to the correct version number, instead of RELEASE.
>
> For sure is a bug on flexmojos, but I have no clue where should start
> looking to fix.
>
> VELO
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en

http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---

Reply via email to