incubator-kalumet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (Created) (JIRA) <>
Subject [jira] [Created] (KALUMET-4) Use global kscript (aka update plan)
Date Tue, 13 Dec 2011 20:51:30 GMT
Use global kscript (aka update plan)

                 Key: KALUMET-4
             Project: Apache Kalumet
          Issue Type: New Feature
          Components: common-model, console
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré
             Fix For: 0.6-incubating

Currently, Kalumet uses the following "hardcoded" update plan:
- update the "pre J2EE" softwares
- update the J2EE application server resources (data sources, JMS connection factories, etc)
- update J2EE application (archives, configuration files, etc)
- update the "post J2EE" softwares

In the softwares, we use a fully custom "update plan", allowing the users to orchestrate location,
configuration files, etc.

It makes sense to use the software approach globally.

It means that we will provide a palette of "script units" (J2EE application server, middlewares,
locations, configuration files, etc) and allow the users to describe the update plan named
a kscript.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message