> -----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)
>
>
> > -----Original Message-----
> > From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > Sent: 25. mars 2003 21:57
> > To: 'Maven Users List'
> > Subject: Container start/stop + packaging (was RE: WebLogic Server
> > plugin)
> >
> >
> > Hi Michal,
> >
> > Some ideas about container start/stop and application packaging:
> >
> > * The Cactus project is currently starting/stopping/configuring several
> > containers (Orion, Resin, JBoss, WebLogic, Tomcat, etc). We have
> > recognized that this is not Cactus specific and are slowly working
> > towards externalizing this (we're lacking time ATM unfortunately).
> >
> > * We would potentially like to start a jakarta-commons project, whose
> > goal would be to provide an "API" for starting/stopping containers and
> > then provide an "SPI" for the different containers. Maybe another
> > project in jakarta-commons would be in charge of generating completely
> > configured applications (including directory structure and config files
> > for a given app server)
> >
>
> This sounds like a very interesting approach. If I understand you
> correctly,
> you would like to move the start/stop logic currently in Cactus
> and Maven's
> appserver plugin to this new project. I suggest the name "Jakarta Commons
> Appserver" (Container is too generic and J2EE is discriminating for app
> servers like Tomcat and Jetty).
>
I think that idea is very cool.
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 know what are the objectives for Maven project.
But I would like to see what we call Maven now, more thinner and equipped
only with
set of real core plugins. Other plugins should be easily
downloadable/deployable
only on user demand.
I think if such separation would happen why not to create subproject
directly under Maven?
I see possibly a lot of categories of projects:
0) Everything related to repository access
1) Appserver Control API
2) Version Control API (unified access to CVS, SVN, VSS ) etc
3) Issue Tracking System API (pure Java API for accessing JIRA, Scarab etc)
4) Continuous integration build system
5) Maven IDE
6) etc..
[..]
[..]
regards
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
