Right now the know fix is to use maven 2.0.10

Sent from DROID

Em 12/02/2010 21:28, "Ronak Patel" <[email protected]>escreveu:

I can second this. I see this when I build the war file module itself.
When I do a top level build, the value gets substituted properly.

Any ideas?

On Jan 25, 3:07 am, velo <[email protected]> wrote:
> > I'm trying with the example on svn at:
> >  flexmojos/flexmojos-testing/flexmojos-test-harness/projects/concept/
> >copy-flex-resources
> > replacing the value of %{flexmojos.version} with 3.4.2 and 3.5.0 or
> > 3.6-SNAPSHOT in both child modules pom.xml (BTW how does this special
> > property syntax work?)
>
> Black magic ;)
>
> I do use and special interpolator that does look for %{variable}
> instead of ${variable}.  That way I can keep maven ${variables}
> untouched but still enforce the right version of flexmojos gets
> executed on ITs.
>
>
>
> > if I issue "mvn clean install" from thecopy-flex-resourcesdir
> > everything is ok, if I go into the war subdir and I launch it again I
> > get the file with the wrong name: ${project.artifactId}-$
> > {project.version}.swf
>
> ok, I can try that, did you filed a ticket?
>
> VELO


-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
T...
http://flexmojos.sonatype.org/

-- 
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://flexmojos.sonatype.org/

Reply via email to