On Sat, Jul 30, 2005 at 11:36:24PM +0200, joerg wrote: > Hey there, > > I am back on the list after over one year. I have actively used maven1 > in various projects. I liked it but also suffered under some aspects.
Welcome back! > Now I had a look at m2: > > It seems that m2 will have the ability to categorize dependencies (test, > compile-time, run-time). This is awesome and was something I missed a > lot in m1. > > It seems that m2 will support "recursive dependencies". This is also a > great idea. It might cause some trouble when e.g. a Project A depends on > B and C while B and C both depend on D but in different versions. > I guess this problem is not new to you guyz and we all had and have such > problems with or without maven. 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. Right now the only implementation is that "nearest wins" so you can override the version by having a dependency in your project's pom. The strategy is pluggable to it will be possible to change this later. > It seems that sub-projects (in that "mulitproject" thingy) do not define > their dependency to its parent project by a filesystem reference but a > repository reference and the POM of the parent project that has to be > deployed there before. Again I have to say "great" - this will allow > you to check out only an single sub-project from a huge project > and build it directly from that point. > > It seems that you've decided to kick out jelly and build plugins > (usually) as native java classes. Concratulations! This is the best > thing you could do. Maybe m2 will be reasonable fast. m2 *is* resonably fast :) All core plugins are written in Java although it's possible to script the plugins in either Marmalade or BeanShell. Adding support for other languages is very easy. > 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. > 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 :)). You have some important links > not yet on the site (wiki?, ...). I did not read deep into the history > of this dev-list so maybe you have a few important mails in some > mailfolder that you could just forward... If you really want to get into the Maven 2 code itself, I'd say that the best place is to start is in the m2 sources. Now, if you only want to look into using Maven 2 I'd say; start using Maven 2. I'm sure that by doing either one of those two you'll run into something that we can improve. > 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. Not sure what you mean, there are hardly any projects in the Maven source tree that actually configured the source directory. > > So now I will try to get a little into the source (understanding plexus > and all this kind of stuff) - might take me some weeks to become into, > however. Have fun! :) -- Trygve
signature.asc
Description: Digital signature
