Well what should I say?

I upgraded to 3.6 and it stopped working, so I upgraded to 3.6.1 and saw
that here was the same behaviour ... downgraded to 3.5 ... still the same
and when I came back to 3.4.2 everything was ok. As I need the 3.5+ stuff
for flex4 I decided to try using 3.6.1 in the build and 3.4.2 in the
packaging and that worked. I could make a viedeo of this to proove it ;-)

Chris

2010/4/19 Marvin Froeder <[email protected]>

> There are tickets open about that, it is a maven bug, so I find hard to
> believe the only thing you changed was flexmojos version....
>
> VELO
>
>   On Mon, Apr 19, 2010 at 5:51 PM, Christofer Dutz <
> [email protected]> wrote:
>
>>   Another thing,
>>
>> the artifacts are all build correctly. The files have the correct names
>> and are correctly installed in my local reository. The only thing that seems
>> to be failing, is the flexmojo swf-copy-thingy that seems to not evaluate
>> the placeholders ... but only when being invoked by "mvn
>> jetty:run-exploded". When doing a "mvn clean install" of the entire project,
>> everything is ok.
>>
>>
>> Chris
>>
>>  2010/4/19 Marvin Froeder <[email protected]>
>>
>>> Hrmmm, never noticed that, you are probably doing something you
>>> shouldn't.....
>>>
>>>
>>> flex.output means nothing on flexmojos, all depends on how are you using
>>> it, but AFIK, maven will interpolate
>>> ${project.artifactId}-${project.version} to you current project..... so
>>> depends how you are using that you are just telling flexmojos to use that
>>> same string as final destination to all SWF.
>>>
>>>
>>> VELO
>>>
>>>
>>> On Mon, Apr 19, 2010 at 4:54 PM, Christofer Dutz <
>>> [email protected]> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am currently confused about the following behaviour, which I think
>>>> is not the way it's meant to be. I recently updated my flexmojos
>>>> version in my build from 3.4.2 to 3.6.1 and am sort of anoyed by this:
>>>>
>>>> When I build my multi-module Spring + Flex application everything
>>>> builds fine. Even the War is exaclty the way it should be. If I want
>>>> to start the server in order to debug it, I usually start it in
>>>> IntelliJ using "mvn clean jetty:run-exploded". This worked fine for
>>>> quite some time. As soon as I execute this now, all SWF resources are
>>>> copied to the War directory with the name "${project.artifactId}-$
>>>> {project.version}.swf" every one overwriting the last one. As soon as
>>>> I go back to 3.4.2 just for the resource copying in my war-project,
>>>> everything is fine and this is the way I am currently working: The
>>>> whole project uses 3.6.1 and the War Project is set to 3.4.2.
>>>>
>>>> One thing might help in diagnosing the cause:
>>>> In order to be able to debug my 14-Module Flex application (I'm
>>>> talking about 13 dynamically loaded swf-modules) I created profiles in
>>>> my pom to compile the swfs to the main modules directory:
>>>>
>>>>    <profiles>
>>>>        <profile>
>>>>            <id>default</id>
>>>>            <properties>
>>>>                <!-- Build the project into the target of the main
>>>> application. -->
>>>>                <flex.output>${basedir}/target/${project.artifactId}-$
>>>> {project.version}.swf</flex.output>
>>>>            </properties>
>>>>        </profile>
>>>>        <profile>
>>>>            <id>debug</id>
>>>>            <properties>
>>>>                <!-- Build the project into the target of the main
>>>> application. -->
>>>>                <flex.output>
>>>>                    ${basedir}/../../ee-webapp/modules/client/modules/
>>>> application/target/${project.artifactId}-${project.version}.swf
>>>>                </flex.output>
>>>>            </properties>
>>>>        </profile>
>>>>    </profiles>
>>>>
>>>> As this string is exactly the one used for the default profile, I am
>>>> guessing, that something must have changed here ...
>>>>
>>>> Currently I'll just stick to the dual-version solution, but I just
>>>> thought I should post this.
>>>>
>>>> Keep up the good work :-)
>>>>
>>>>      Chris
>>>>
>>>> --
>>>> 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]<flex-mojos%[email protected]>
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/flex-mojos
>>>>
>>>> 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]<flex-mojos%[email protected]>
>>> For more options, visit this group at
>>> http://groups.google.com/group/flex-mojos
>>>
>>> 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]<flex-mojos%[email protected]>
>> For more options, visit this group at
>> http://groups.google.com/group/flex-mojos
>>
>> 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]<flex-mojos%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos
>
> 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

http://flexmojos.sonatype.org/

Reply via email to