You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Vincent Massol <vm...@pivolis.com> on 2003/03/25 21:56:56 UTC

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)

* Obviously this project would implement the upcoming JSR (117 or
something like that - Not sure if this JSR is only about deployment or
if it also about starting/stopping containers)

* Anyway, we believe it is better to implement this in a commons project
rather than in a Maven plugin as an important feature is that it should
be able to start/stop containers from different front ends (Maven, Ant,
Eclipse, etc).

* ATM, the way Cactus implements container start/stop and application
packaging is using Ant. This allows us to reuse the Ant scripts from the
Maven plugin, from Ant (of course) and also from our Eclipse plugin
(which internally calls Ant).

I'm curious to know what others think? 

Thanks
-Vincent

> -----Original Message-----
> From: michal.maczka [mailto:michal.maczka@cqs.ch]
> Sent: 25 March 2003 13:18
> To: Maven Users List
> Subject: RE: WebLogic Server plugin
> 
> It think that definitely the best place for it would be appserver
plugin.
> 
> Maybe you can look at Cactus plugin? There is a part of such
functionality
> implemented there.
> 
> I think once more such plugins like yours exists it will be easier to
see
> how to control
> different application server in common manner + make plugins like
Cactus
> use appserver plugin.
> 
> 
> Michal
> 
> 
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: Aslak Hellesøy [mailto:aslak.hellesoy@netcom.no]
> > Sent: Tuesday, March 25, 2003 9:37 AM
> > To: Maven Users List
> > Subject: WebLogic Server plugin
> >
> >
> > Hi!
> >
> > A colleague and I have been working on a weblogic plugin for Maven.
This
> > plugin has the following functionality:
> >
> > o Stub-generation with weblogic.ejbc
> > o JSP compilation with weblogic.jspc
> > o Deployment of J2EE components (EAR, WAR and EJB) using the
> > weblogic.deploy
> > class
> > o Execution of WLShell scripts (see http://tinyurl.com/83ns)
> > o Creation of empty weblogic domains (from a template included in
the
> > plugin)
> >
> > 1) Has anyone else been working on this?
> >
> > 2) Would anyone be interested if we contributed this plugin to
Maven?
> >
> > 3) In
maven/src/plugins-build/examples/exampleear-1.0/project.properties
> > there are some maven.weblogic.* properties. I can't see these being
used
> > anywhere. Can anyone enlighten me on what these were intended for?
> >
> > Cheers,
> > Aslak
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Container start/stop + packaging (was RE: WebLogic Server plugin)

Posted by "michal.maczka" <mi...@cqs.ch>.

>
> > -----Original Message-----
> > From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> > 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Container start/stop + packaging (was RE: WebLogic Server plugin)

Posted by Vincent Massol <vm...@pivolis.com>.

> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> 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:

<my domain name>
  |_ applications
    |_ myear.ear
  |_ lib
    |_ [some jars that need to be put in the system cp]
  |_ classes
    |_ [some classes that need to be put in the system cp]
  |_ config.xml
  |_ DefaultAuthenticatorInit.ldift
  |_ fileRealm.properties
  |_ SerializedSystemIni.dat
  |_ wlDefaultKeyStore.jks
  |_ startContainer.cmd|startContainer.sh
  |_ stopContainer.cmd|stopContainer.sh

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 believe the start/stop project and this packaging project should be 2
separate projects.

Ideas? Comments?

Thanks
-Vincent

> 
> I also work closely with WebSphere and have start/stop jelly scripts
for
> that at the moment.
> --
> dIon Gillard, Multitask Consulting
> Blog:      http://www.freeroller.net/page/dion/Weblog
> Work:      http://www.multitask.com.au
> 
> 
> "Vincent Massol" <vm...@pivolis.com> wrote on 26/03/2003 07:56:56
AM:
> 
> > 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)
> >
> > * Obviously this project would implement the upcoming JSR (117 or
> > something like that - Not sure if this JSR is only about deployment
or
> > if it also about starting/stopping containers)
> >
> > * Anyway, we believe it is better to implement this in a commons
project
> > rather than in a Maven plugin as an important feature is that it
should
> > be able to start/stop containers from different front ends (Maven,
Ant,
> > Eclipse, etc).
> >
> > * ATM, the way Cactus implements container start/stop and
application
> > packaging is using Ant. This allows us to reuse the Ant scripts from
the
> > Maven plugin, from Ant (of course) and also from our Eclipse plugin
> > (which internally calls Ant).
> >
> > I'm curious to know what others think?
> >
> > Thanks
> > -Vincent
> >
> > > -----Original Message-----
> > > From: michal.maczka [mailto:michal.maczka@cqs.ch]
> > > Sent: 25 March 2003 13:18
> > > To: Maven Users List
> > > Subject: RE: WebLogic Server plugin
> > >
> > > It think that definitely the best place for it would be appserver
> > plugin.
> > >
> > > Maybe you can look at Cactus plugin? There is a part of such
> > functionality
> > > implemented there.
> > >
> > > I think once more such plugins like yours exists it will be easier
to
> > see
> > > how to control
> > > different application server in common manner + make plugins like
> > Cactus
> > > use appserver plugin.
> > >
> > >
> > > Michal
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Aslak Hellesøy [mailto:aslak.hellesoy@netcom.no]
> > > > Sent: Tuesday, March 25, 2003 9:37 AM
> > > > To: Maven Users List
> > > > Subject: WebLogic Server plugin
> > > >
> > > >
> > > > Hi!
> > > >
> > > > A colleague and I have been working on a weblogic plugin for
Maven.
> > This
> > > > plugin has the following functionality:
> > > >
> > > > o Stub-generation with weblogic.ejbc
> > > > o JSP compilation with weblogic.jspc
> > > > o Deployment of J2EE components (EAR, WAR and EJB) using the
> > > > weblogic.deploy
> > > > class
> > > > o Execution of WLShell scripts (see http://tinyurl.com/83ns)
> > > > o Creation of empty weblogic domains (from a template included
in
> > the
> > > > plugin)
> > > >
> > > > 1) Has anyone else been working on this?
> > > >
> > > > 2) Would anyone be interested if we contributed this plugin to
> > Maven?
> > > >
> > > > 3) In
> > maven/src/plugins-build/examples/exampleear-1.0/project.properties
> > > > there are some maven.weblogic.* properties. I can't see these
being
> > used
> > > > anywhere. Can anyone enlighten me on what these were intended
for?
> > > >
> > > > Cheers,
> > > > Aslak
> > > >
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > >
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Container start/stop + packaging (was RE: WebLogic Server plugin)

Posted by di...@multitask.com.au.
I'd much rather it was 'pure' java rather than Ant tasks as the 
implementation.

I also work closely with WebSphere and have start/stop jelly scripts for 
that at the moment.
--
dIon Gillard, Multitask Consulting
Blog:      http://www.freeroller.net/page/dion/Weblog
Work:      http://www.multitask.com.au


"Vincent Massol" <vm...@pivolis.com> wrote on 26/03/2003 07:56:56 AM:

> 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)
> 
> * Obviously this project would implement the upcoming JSR (117 or
> something like that - Not sure if this JSR is only about deployment or
> if it also about starting/stopping containers)
> 
> * Anyway, we believe it is better to implement this in a commons project
> rather than in a Maven plugin as an important feature is that it should
> be able to start/stop containers from different front ends (Maven, Ant,
> Eclipse, etc).
> 
> * ATM, the way Cactus implements container start/stop and application
> packaging is using Ant. This allows us to reuse the Ant scripts from the
> Maven plugin, from Ant (of course) and also from our Eclipse plugin
> (which internally calls Ant).
> 
> I'm curious to know what others think? 
> 
> Thanks
> -Vincent
> 
> > -----Original Message-----
> > From: michal.maczka [mailto:michal.maczka@cqs.ch]
> > Sent: 25 March 2003 13:18
> > To: Maven Users List
> > Subject: RE: WebLogic Server plugin
> > 
> > It think that definitely the best place for it would be appserver
> plugin.
> > 
> > Maybe you can look at Cactus plugin? There is a part of such
> functionality
> > implemented there.
> > 
> > I think once more such plugins like yours exists it will be easier to
> see
> > how to control
> > different application server in common manner + make plugins like
> Cactus
> > use appserver plugin.
> > 
> > 
> > Michal
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Aslak Hellesøy [mailto:aslak.hellesoy@netcom.no]
> > > Sent: Tuesday, March 25, 2003 9:37 AM
> > > To: Maven Users List
> > > Subject: WebLogic Server plugin
> > >
> > >
> > > Hi!
> > >
> > > A colleague and I have been working on a weblogic plugin for Maven.
> This
> > > plugin has the following functionality:
> > >
> > > o Stub-generation with weblogic.ejbc
> > > o JSP compilation with weblogic.jspc
> > > o Deployment of J2EE components (EAR, WAR and EJB) using the
> > > weblogic.deploy
> > > class
> > > o Execution of WLShell scripts (see http://tinyurl.com/83ns)
> > > o Creation of empty weblogic domains (from a template included in
> the
> > > plugin)
> > >
> > > 1) Has anyone else been working on this?
> > >
> > > 2) Would anyone be interested if we contributed this plugin to
> Maven?
> > >
> > > 3) In
> maven/src/plugins-build/examples/exampleear-1.0/project.properties
> > > there are some maven.weblogic.* properties. I can't see these being
> used
> > > anywhere. Can anyone enlighten me on what these were intended for?
> > >
> > > Cheers,
> > > Aslak
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Container start/stop + packaging (was RE: WebLogic Server plugin)

Posted by "michal.maczka" <mi...@cqs.ch>.

> -----Original Message-----
> From: vmassol@pivolis.com [mailto:vmassol@pivolis.com]
> 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" <mi...@cqs.ch>:
>
> >
> >
> > > -----Original Message-----
> > > From: Aslak Hellesøy [mailto:aslak.hellesoy@netcom.no]
> > > 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Container start/stop + packaging (was RE: WebLogic Server plugin)

Posted by vm...@pivolis.com.
Hi Michal,

Quoting "michal.maczka" <mi...@cqs.ch>:
 
> 
> 
> > -----Original Message-----
> > From: Aslak Hellesøy [mailto:aslak.hellesoy@netcom.no]
> > 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.

Putting it under a given tool's umbrella is dangerous as it may incite tying 
it to that tool thus making it not reusable by other projects. We've had this 
example with Ant and the Zip task for example. I would rather have seen the 
zip code as a commons project and then write a wrapper for Ant than the other 
way around.


> 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.

sure. This is the direction.

> 
> I think if such separation would happen why not to create subproject
> directly under Maven?

I don't view this project as a Maven plugin, nor being Maven related. It is as 
much Centipede-related, Ant-related as it is Maven-related...

That said, I do agree that there will be a Maven plugin that *wraps* around 
this API to make it easily usable by Maven users.

> 
> 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..

I agree with all of these but only for plugins. I believe we should be *very* 
careful not to implement business logic in the plugin itself. In other word, 
the plugin should wrap existing frameworks.

For example, the checkstyle plugin wraps the checkstyle framework and that is 
good. Same with all the others. This provides reusability.

Things that could be separated from Maven (and this is the plan as defined by 
Jason) are for example:
- SCM code 
- API for downloading/uploading to a remote repository

What do yout think?

Thanks
-Vincent

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Container start/stop + packaging (was RE: WebLogic Server plugin)

Posted by "michal.maczka" <mi...@cqs.ch>.


> -----Original Message-----
> From: Aslak Hellesøy [mailto:aslak.hellesoy@netcom.no]
> 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:vmassol@pivolis.com]
> > 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Container start/stop + packaging (was RE: WebLogic Server plugin)

Posted by Aslak Hellesøy <as...@netcom.no>.
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> 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).

> * Obviously this project would implement the upcoming JSR (117 or
> something like that - Not sure if this JSR is only about deployment or
> if it also about starting/stopping containers)
>

JSR 117 is about J2EE Application Availability. I think you mean JSR 88 (The
J2EE Deployment API):
http://java.sun.com/j2ee/tools/deployment/
http://www.jcp.org/en/jsr/detail?id=88

However, the J2EE Deployment API says nothing about starting and stopping
servers (only about J2EE components). AFAIK there is no JSR or standard API
for that.

> * Anyway, we believe it is better to implement this in a commons project
> rather than in a Maven plugin as an important feature is that it should
> be able to start/stop containers from different front ends (Maven, Ant,
> Eclipse, etc).
>

I agree.

> * ATM, the way Cactus implements container start/stop and application
> packaging is using Ant. This allows us to reuse the Ant scripts from the
> Maven plugin, from Ant (of course) and also from our Eclipse plugin
> (which internally calls Ant).
>

It can be implemented as pure java classes (no ties to Ant) and still be
possible to use from Ant. It is no longer necessary to extend Ant's Task
class in order to be used in a <taskdef>. The only thing you need is an
execute() method. If a "proper" Ant task is really needed, I'd prefer it as
a simple wrapper around the "core" API. (I hate it when useful functionality
is too tightly integrated with Ant.)

> I'm curious to know what others think?
>

It would be really nice to add a broader set of functionality than
start/stop to this API:

o A high level API for configuration of an Appserver (setting up JDBC
Connection pools, JMS etc)
o JSP and EJB precompilation (not sure if this belongs in Vincent's proposed
Commons API though)

Cheers,
Aslak

> Thanks
> -Vincent
>
> > -----Original Message-----
> > From: michal.maczka [mailto:michal.maczka@cqs.ch]
> > Sent: 25 March 2003 13:18
> > To: Maven Users List
> > Subject: RE: WebLogic Server plugin
> >
> > It think that definitely the best place for it would be appserver
> plugin.
> >
> > Maybe you can look at Cactus plugin? There is a part of such
> functionality
> > implemented there.
> >
> > I think once more such plugins like yours exists it will be easier to
> see
> > how to control
> > different application server in common manner + make plugins like
> Cactus
> > use appserver plugin.
> >
> >
> > Michal
> >
> >
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Aslak Hellesøy [mailto:aslak.hellesoy@netcom.no]
> > > Sent: Tuesday, March 25, 2003 9:37 AM
> > > To: Maven Users List
> > > Subject: WebLogic Server plugin
> > >
> > >
> > > Hi!
> > >
> > > A colleague and I have been working on a weblogic plugin for Maven.
> This
> > > plugin has the following functionality:
> > >
> > > o Stub-generation with weblogic.ejbc
> > > o JSP compilation with weblogic.jspc
> > > o Deployment of J2EE components (EAR, WAR and EJB) using the
> > > weblogic.deploy
> > > class
> > > o Execution of WLShell scripts (see http://tinyurl.com/83ns)
> > > o Creation of empty weblogic domains (from a template included in
> the
> > > plugin)
> > >
> > > 1) Has anyone else been working on this?
> > >
> > > 2) Would anyone be interested if we contributed this plugin to
> Maven?
> > >
> > > 3) In
> maven/src/plugins-build/examples/exampleear-1.0/project.properties
> > > there are some maven.weblogic.* properties. I can't see these being
> used
> > > anywhere. Can anyone enlighten me on what these were intended for?
> > >
> > > Cheers,
> > > Aslak
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org