> > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: 25 March 2003 22:20 > > To: Maven Users List > > Subject: Re: Container start/stop + packaging (was RE: WebLogic Server > > plugin) > > > > I'd much rather it was 'pure' java rather than Ant tasks as the > > implementation. > > Agreed. However, we may not be talking exactly about the same thing. > There are several features that I'd like to see (in one or several > projects): > > 1/ start/stop of containers. I agree that a Java API is the best for > this. Actually the Ant project already has an interface for that and > several tasks for different containers. The new project could use those > as a start point (we could ask/help Ant to them make use of them in the > existing tasks). > > 2/ fully packaging an application for a given container (and for a given > environment). For example, if I am using weblogic, it would generate a > zip with the following: > <cut/>
> The way I see it, this project would provide these default files (with > basic default values - best guesses) but the user would also be able to > supply them (i.e. pass them as input). Note: This is what is done by the > Cactus Ant Integration for all containers > > For this project, I believe a Java API is not the best. Ant seems to me > the best common denominator. I may be wrong though. > I think that you were right last time. Don't link it with any tool or scripting language. I am sorry to see project like XDoclet, which are basically unusable without Ant. Ant is just greater. But why to be so limited? I suppose that in some cases it might be even necessary to wrap ANT in Java classes (e.g. for SUN One appserver). Scripts and scripting languages are nice for simple things. But they are causing maintanace nightmare and it is extremely painful to test them or to see if they are broken. I think that if more things in Maven were done in pure Java, Maven would be miles ahead. That is why I am happy to see in Maven's road map document the idea of having pure Java API for plugins > I believe the start/stop project and this packaging project should be 2 > separate projects. > > Ideas? Comments? > I don't also think that that is such important how many project there should be for this. Let's just make one. Once there will be a need o splitting a code into projects, subprojects etc we should bother. Centralized efforts are usualy more coherent. I am neither Maven committer nor a committer for any project at Jakarta , but again I would rise a point that Jakarta is for _SERVER_SIDE_JAVA_ and is not the best place for such project. "Jakarta is a Project of the Apache Software Foundation, charged with the creation and maintenance of commercial-quality, open-source, server-side solutions for the Java Platform, based on software licensed to the Foundation, for distribution at no charge to the public". What we are speaking about something is not really "a server side solution". I think that it can be that Maven site is a better place for such efforts. That's why I am asking if Maven should not become something more then it is now - and also host other projects related to Software Engineering. I know that for example Ant is also top level project. > Thanks > -Vincent That is just my personal opinion on this subject. regards Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
