Hi all,
Seems that my initial post has been eaten by the spam filter so I'll try
again...

Switching from Maven2 to Maven3, everything went fine except for the wrapper
goal that is triggered on the war module. No placeholder substitution is
occurring anymore... Running the same build with Maven2 does the job
correctly.

I've also tried with the "issue 102" test
harness<https://github.com/Flexmojos/flexmojos/tree/flexmojos-4.x/flexmojos-testing/flexmojos-test-harness/projects/issues/flexmojos-102/war>and
it's the same.

Is FM 3.8 supported for running with Maven3 ? Note that I have tried with
both 3.8 and 4.0-beta-7.
Does anyone use the wrapper goal with Maven3 successfully ? Do you use an
alternative technique ?

For the sake of completeness, here is the POM section regarding the FM
invocation on the WAR :

      <plugin>
        <groupId>org.sonatype.flexmojos</groupId>
        <artifactId>flexmojos-maven-plugin</artifactId>
        <executions>
          <execution>
            <phase>prepare-package</phase>
            <goals>
              <goal>wrapper</goal>
              <goal>copy-flex-resources</goal>
            </goals>
            <configuration>
              <wrapperArtifact>
                <groupId>${project.groupId}</groupId>
                <artifactId>hrsample-startup-flex-client</artifactId>
              </wrapperArtifact>
              <templateInclusions>
                <String>**/flex/*.html</String>
              </templateInclusions>
              <templateExclusions>
                <String>**/flex/*.js</String>
              </templateExclusions>
              <stripVersion>true</stripVersion>
              <webappDirectory>${project.build.directory}/${project.
artifactId}/flex</webappDirectory>
            </configuration>
          </execution>
        </executions>
      </plugin>


Reading the HtmlWrapperMojo sources, it seems that the trick is to
dynamically change the war plugin configuration to make its
warSourceDirectory reference the ${workDirectory}/wrapped-
template which is where the templates have been processed (that happens
correctly).
This is what doesn't seem to work anymore with Maven 3.

Haven't found any workaround yet, so thank you in advance for any hint.

Vincent

-- 
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