Hrmm, not really. dumpConfigAttach only set if it is gonna be recorded at local repo or not.
On Oct 7, 12:20 pm, "[email protected]" <[email protected]> wrote: > Setting dumpConfigAttach = false doesn't stop the flex compiler from > dumping the config. Below seems to be the offending piece of code in > AbstractFlexCompilerMojo.java. Shouldn't this return null when > dumpConfigAttach = false? > > public String getDumpConfig() > { > File dumpConfig = new File( getTargetDirectory(), > getFinalName() + "-" + CONFIGS + "." + XML ); > > if ( dumpConfigAttach ) > { > if ( getClassifier() != null ) > { > getLog().warn( "Config dump is not attached for > artifacts with classifier" ); > } > else > { > projectHelper.attachArtifact( project, XML, CONFIGS, > dumpConfig ); > } > } > return PathUtil.path( dumpConfig ); > } -- 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/
