On Sat, Aug 29, 2009 at 4:47 PM, David Rom <[email protected]> wrote:
> It works with the parent build, but breaks with the module build.
>> When I build the war module the ${build.finalName} property gets
>> replaced with ${project.artifactId} rather than the actual artifact
>> file name. I think something must have changed with the way maven
>> handles properties, but I don't know enough about maven (or Flexmojos)
>> to offer a better explanation. I'll add an issue to JIRA for this and
>> do my best to clean up the example you looked at so it illustrates the
>> behavior. For myself, I will simply use maven 2.0.10.
>>
> Hmmm... that's weird. Velo might know better about the differences or
> even already have a general strategy of dealing with 2.0.9 vs 2.2.x issues.
> I think I remember seeing some other threads on the group where that was
> discovered to be the root cause of their problems, but I don't remember
> offhand if they were ever resolved (other then by, like you, reverting back
> to 2.0.9/10).
>
I don't think there is much I can do.... specially if it is a maven bug =/
I will try to look into it, eventually =D
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/
-~----------~----~----~----~------~----~------~--~---
