Thanks for your kind words! Others have already answered most of this, so I'll just cover a couple of extra things.
joerg wrote: > Anyways I'd like to know your ideas how > to handle this issue in m2 (there should be a way for the m2 user to > manually decide which version to use - maybe simply by defining the > troublecausing dependency on the toplevel project in the desired > version). Anyways I think that "recursive dependencies" are in general a > good idea. As already pointed out, we have dependency mediation, which there is info on the wiki about. Basically: - the version you give is a suggestion, and it figures out the best one for you - you can specify ranges to ensure you get at least a certain version - once done figuring those out, it will either take the nearest (current), newest (not yet implemented), oldest (nyi), or fail if they don't match (nyi). Other techniques could be plugged in in future. - you can force a certain version to be used from the current POM. You might like to check out https://sydneyjug.dev.java.net/files/documents/922/15554/sjug20050601.pdf which talks about the new features. A newer version as presented at JavaOne/OSCon should be up soon. > > It seems however that m2 is a lot less documented than m1 (is that > possible:) ) and m2 is far beyond from being complete. > Now that's where we go. Since I seem to like your ideas I wonder > if I could get involved a little (do not expect too much cause I > am already involved in another open-source project - that is of cause > using maven). > > Maybe you could help me out getting into m2 a little faster. We've done plenty of doco on the site about plugin development (the mojo API and the build lifecycle). It could be better, but combined with the current examples we hope its enough to get started. What we really need help with is: - documentation: http://maven.apache.org/maven2/docs-required.html - writing plugins: http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix > I do not have a clue what the actual state of m2 is (are you still > planning important architectural decicisions or is everyting clear > and just some code missing :)). As Jason said, we are nearly feature complete and about to hit beta, so only plugin development and bugfixes from here on until about October when we will start on Maven 2.1 :) > BTW it seems that the POM inheritance in subprojects is not yet working > properly. I had to define things like folders (that src/main/java, ... > stuff) and specific settings (JDK 5.0 compliance, funny that it is still > -source 1.5 and not 5.0) in every subproject. This has been tested - so if you have a reproducible failure, please post it to JIRA. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
