I've got a multimodule project that builds both flex and java artifacts in
different modules.
The flexmojos pieces build just fine with 4.0-beta-7. I've got it split up
with a common SWC module that gets included into two different swf modules.
When I run the mvn site plugin with certain reports configured (surefire
report plugin 2.8.1 is one of them that triggers the behavior) - the swc
dependency will build, but when it builds the swf file it has a lot of
errors about methods and things it can't find (methods and things that come
from the swc library)
On my maven parent pom I have it configured like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.0-beta-3-SONATYPE-r1000854</version>
<configuration>
<reportPlugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.2</version>
<configuration>
<dependencyDetailsEnabled>true</dependencyDetailsEnabled>
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changelog-plugin</artifactId>
<version>2.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-report-plugin</artifactId>
<version>2.8.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>2.5</version>
<configuration>
<linkXref>true</linkXref>
<sourceEncoding>utf-8</sourceEncoding>
<minimumTokens>100</minimumTokens>
<targetJdk>1.6</targetJdk>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jxr-plugin</artifactId>
<version>2.2</version>
<configuration>
<aggregate>false</aggregate>
<linkJavadoc>false</linkJavadoc>
</configuration>
</plugin>
</reportPlugins>
</configuration>
</plugin>
The swc and swf compile file in a normal build - it's when I run it through
the site plugin when it starts to have problems. Is there some way to
specify that it shouldn't execute durring the "site" part of the lifecycle?
or if it does execute in that lifecycle, at least have it resolve the
dependencies properly so it can actually build?
--
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/