On 2008.03.28., at 15:35, Wayne Fay wrote:
In the future, you might just go right to the source and ask the originating team responsible for the code why it doesn't compile. So in this case, ask Atlassian directly.
Not being able to run "mvn eclipse:eclipse" (and several other fairly straightforward mvn tasks) seemed generic enough to me that I assumed it is a problem with my Maven setup and not in the project I tried to work with. The Maven's error message was less than helpful in explaining what's going on, and digging the web with Google for the error message also didn't yield satisfactory results.
(IMO the Maven users list cannot possibly hope to support every single developer who stumbles across an open-source project that uses Maven as their build tool and then has a problem building the code. So most questions like these should be sent to the responsible development team first, then if they can't help you can forrward it here. You may be doing them a favor by notifying them of a problem they didn't even know they had! )
I agree - I often end up saying the same to Struts 2 users when they're seeking help on the FreeMarker list :-)
Again, the conclusion I reached based on the observed symptoms was that this is a Maven issue. Actually, it *is* a Maven issue; why would Maven2 be allowed to break in such an ugly manner when facing a Maven1- compliant project? Some sort of version mismatch detection and a clean fail-fast behavior with an explanatory error message would be in order, methinks... Would certainly reduce the kind of mailing list traffic that you'd like to avoid :-)
Thanks to Nick for help, Attila. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
