> -----Original Message----- > From: Julian Scheid [mailto:[EMAIL PROTECTED] > Sent: Monday, June 28, 2004 5:45 AM > To: [EMAIL PROTECTED] > Subject: Self-dependent plugin > > > Hello Maven friends, >
> In general, what do Maven experts think: is the Maven architecture > prepared for self-dependent projects like this, or should I better > stick to the lower-level approach, Ant, for this particular kind of > project? > I don't think that Maven is prepared for such uses case. Generally it is not good idea to introduce such self dependency early in life cycle of the project. In the best case incremental development should work. Eg. you have fully functional version 0.1 of your tool and you are working on version 0.2 but internally you should be using version 0.1 for building version 0.2 Bootstrap system for maven1 is written using ant, for maven2 using unix scripts. IMO such solution is needed in initial phases of development. When project matures things might look differently. For example CVS sources are kept in CVS, SVN sources are kept in SVN repository, Javacc uses javacc for parsing its grammar files, AFAIK Ant can be also build with ant. This is just a sign of maturity of given project and requires that at least one fully reliable version exits and futures which are used internally don't go beyond this version. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
