> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 26, 2003 12:03 PM > To: Maven Users List; michal.maczka > Subject: RE: Container start/stop + packaging (was RE: WebLogic Server > plugin) > > > Hi Michal, > > Quoting "michal.maczka" <[EMAIL PROTECTED]>: > > > > > > > > -----Original Message----- > > > From: Aslak Helles�y [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, March 25, 2003 10:46 PM > > > To: Maven Users List > > > Subject: RE: Container start/stop + packaging (was RE: WebLogic > > Server > > > plugin) > > [snip] > > > > > As I understand the purpose of at Jakarta Commons, components developed > > under this initiative > > should be highly reusable across many projects. > > This set of API which we are discussing id rather not that > > "frequently needed". > > > > Maybe Maven itself can open an umbrella for development of such > > subprojects? > > > > > I don't think it belongs to Maven. In the same way as I wouldn't > put it under > the Eclipse project umbrella. It is something more generic that > can be used by > Maven plugins, by Eclipse plugins, etc. >
I agree in 100%. But I was trying to say that AFAIK there exist no common and good place for such things. I don't think that Jakarta Commons is the right place for such efforts. Once Maven was promoted to Top Level Apache project (is it now equally importand in Apache hierachy as Jakarta?) maybe Maven can become much more than it is now and also host other projects which are providing tools for Software Engineering? Then what we call Maven now will be just a part of this "big whole" and will profit from outcome of other projects. For example one of hosted project could be Classworlds, other Appserver Control API. That is what I ment. I know that my idea is not yet mature. So I am wating for your critics. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
