On Fri, 2007-08-03 at 13:48 -0700, Matt Benson wrote: > --- Dennis Lundberg <[EMAIL PROTECTED]> wrote: > > I sense I'll not be able to escape M(1|2). Groan, I > was hoping to avoid M2 for some time yet... Let me do > some research to see exactly what I'm getting into if > I opt to switch JXPath. Aren't we now in the mode of > support M1-even-after-adding-M2-support though? That > would make it seem as though I still have to mess with > M1 even if I opt to "upgrade" to M2.
Maven2 really is a whole lot better than maven1. It's *much* faster and *much* stabler. It's also the currently supported version. Yes maven can be rather mysterious at times; I suffer the same pain as you :-). However I can't imagine getting the sort of nice websites we currently have from any other tool without major effort and complexity - at which point we'd all have to learn this new, unique and badly documented system rather than maven. I don't think there's an easy solution to this problem. Probably best to just improve our documentation about how to get Maven to work for us.. There is a nice maven manual available for download called "Better Builds with Maven". See the documentation link on the maven.apache.org site. I don't see why maven1 support is necessary. We do need to deploy to the maven1 repository, so maven1 users can use the release. But there may be easier ways of doing that than writing a complete maven1 buildfile. Most components currently have maven1 builds because they were first converted over before maven2 existed.. BTW, I see that Mergere.com (home of many maven developers) is now DevZuz.com. That had me confused for a while.. Cheers, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
