On Sun, Feb 28, 2010 at 9:45 AM, christoph.pickl <[email protected]> wrote: >> The failure looks to be somehow related to some AOP-based plugin thing >> that hudson wraps the maven plugins with: > > usual answer to that: try to use another (the most current) version of > hudson. > maybe also add the "-X" argument to the mvn command to get some debug > output > and post the last couple of lines before the exception is thrown.
It's a problem with the artifactory plugin for hudson - I reported a bug to them. It's odd because the build I have building the mvn site goal doesn't even make any use of the artifactory plugin at all - yet it seems fit to stick itself into the build process and find a way to break my build for me. Disabling the plugin without changing any other configuration makes the same build work fine - and re-enabling it makes it break in the exact same way. >> One other thing I noticed is that if I do a "mvn clean install site" >> when it comes into the execution to do the site generation, flexmojos >> seems to fire up and compile everything again > > i am not quite sure about that, but as the artifact type is swf and > therefore different from the regular jar, > you get another (flexmojo's defined) lifecycle, and probably thats the > reason why everything gets created/compiled/tested from scratch again, > just for the site generation?! Does it do the same thing for you when you run mvn:site? it does it for me on my local machine as well as on the build server - it's annoying but not a big deal since it takes forever to do the other reports anyway... but it would be nice to cut it out if there was a way to do that. Ryan -- 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?hl=en?hl=en http://flexmojos.sonatype.org/
