On 07/21/2011 08:07 PM, Igor Fedorenko wrote: > If you control the maven plugin, then BuildContext from susi-build-api > is the easiest way to associate problem markers with source files.
Yes, that works pretty well, thanks! Now I don't even need a m2e plugin. Mapping the custom goals to the execute action is enough. But one minor problem still exists: When I just add messages to the build context then the command-line maven doesn't recognize this as a build failure, so I have to throw a MojoExecutionException at the end when a javascript error was detected. But inside Eclipse this always creates an error marker in the pom.xml. Is there a way to avoid this? Would be nice to just have error markers in the javascript files (The BuildContext messages) but the command line maven must still report a build failure when a javascript error occured. -- Bye, K <http://www.ailis.de/~k/> [A735 47EC D87B 1F15 C1E9 53D3 AA03 6173 A723 E391] (Finger [email protected] to get public key) _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
