JBoss Packager

[Michiel Trimpe-2]

Hello everybody,

I'm interested in developing the Packager implementation for JBoss 4.x.

@Matt: You said that this was already available in the latest alpha but I can't find it though.
I've tried using 1.0-SNAPSHOT and looked in SVN but I can only find Packagers for Tomcat.

If there is no Packager for JBoss 4.x. I could use some help with the following:

• JBoss has separate directories for different instances (e.g. ./server/frontend & ./server/backend). Any $.02 on what kind of implications that would have?
• How does the Packager currently deal with filling the ./lib directory? Does it check all 'provided' libraries and install them in ./lib and would that be a good idea if it doesn't yet do that?
• Is there a default way for bringing configuration files along, like copying /src/main/conf* to ./conf?
• If we want to generate different packages for different environments, how should we do that? Add a build-time parameter like /src/main/conf/${environment}/? 

All comments are welcome; this is my first time contributing to an open-source project so I'm probably still a little clumsy as to how the process works.

Regards,

Michiel Trimpe

[Matt Wringe]

We got your first message, please don't send the same email multiple
times to the mailing list.

On Mon, 2008-07-14 at 15:29 +0200, Michiel Trimpe wrote:

> Hello everybody,
>
> I'm interested in developing the Packager implementation for JBoss
> 4.x.
>
> @Matt: You said that this was already available in the latest alpha
> but I can't find it though.
> I've tried using 1.0-SNAPSHOT and looked in SVN but I can only find
> Packagers for Tomcat.
>
> If there is no Packager for JBoss 4.x. I could use some help with the
> following:
>       * JBoss has separate directories for different instances
>         (e.g. ./server/frontend & ./server/backend). Any $.02 on what
>         kind of implications that would have?
>       * How does the Packager currently deal with filling the ./lib
>         directory? Does it check all 'provided' libraries and install
>         them in ./lib and would that be a good idea if it doesn't yet
>         do that?
>       * Is there a default way for bringing configuration files along,
>         like copying /src/main/conf* to ./conf?
>               * If we want to generate different packages for
>                 different environments, how should we do that? Add a
>                 build-time parameter
>                 like /src/main/conf/${environment}/?
> All comments are welcome; this is my first time contributing to an
> open-source project so I'm probably still a little clumsy as to how
> the process works.
>
> Regards,
>
> Michiel Trimpe

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email