You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jian Liao <no...@gmail.com> on 2005/12/10 08:51:11 UTC
How to package all the dependences into a single EAR file?
Hi all,
Could someone tell me how to package all the dependences into a single EAR
file?
I would like to see the following file structure:
jetspeed.ear
|
|------lib (folder which contains all the jar files should be loaded
by EAR level classloader)
|
|------jetspeed.war
|
|------demo.war
|
|------j2-admin.war
|
|------META-INF
......
How to reference the files in "lib" folder in my plan? Should I use "import"
tag?
I want to package all these files into a single EAR file. Any help would be
appreciated!
regards,
- Jian Liao
Re: How to package all the dependences into a single EAR file?
Posted by Jian Liao <no...@gmail.com>.
Thanks for your respond!
On 12/10/05, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>
> The deployment plan doesn't have a specific way to refer to add libs
> within the EAR to the ClassPath (though this would be a pretty
> sensible thing for us to add). The dependency element will add a
> library to the EAR's ClassPath, but then the library has to be located
> in the Geronimo repository (under
> repository/product/jars/abc-1.0.jar).
>
> It may be the case that you can add the libs in the ear to a Manifest
> Class-Path entry for the WAR files in the EAR -- I'm not sure if we
> support this for WAR files.
>
> Aaron
>
> On 12/10/05, Jian Liao <no...@gmail.com> wrote:
> > Hi all,
> >
> > Could someone tell me how to package all the dependences into a single
> EAR
> > file?
> > I would like to see the following file structure:
> >
> > jetspeed.ear
> > |
> > |------lib (folder which contains all the jar files should be
> loaded
> > by EAR level classloader)
> > |
> > |------jetspeed.war
> > |
> > |------demo.war
> > |
> > |------j2-admin.war
> > |
> > |------META-INF
> > ......
> >
> > How to reference the files in "lib" folder in my plan? Should I use
> "import"
> > tag?
> >
> > I want to package all these files into a single EAR file. Any help would
> be
> > appreciated!
> >
> > regards,
> >
> > - Jian Liao
>
Re: How to package all the dependences into a single EAR file?
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
The deployment plan doesn't have a specific way to refer to add libs
within the EAR to the ClassPath (though this would be a pretty
sensible thing for us to add). The dependency element will add a
library to the EAR's ClassPath, but then the library has to be located
in the Geronimo repository (under
repository/product/jars/abc-1.0.jar).
It may be the case that you can add the libs in the ear to a Manifest
Class-Path entry for the WAR files in the EAR -- I'm not sure if we
support this for WAR files.
Aaron
On 12/10/05, Jian Liao <no...@gmail.com> wrote:
> Hi all,
>
> Could someone tell me how to package all the dependences into a single EAR
> file?
> I would like to see the following file structure:
>
> jetspeed.ear
> |
> |------lib (folder which contains all the jar files should be loaded
> by EAR level classloader)
> |
> |------jetspeed.war
> |
> |------demo.war
> |
> |------j2-admin.war
> |
> |------META-INF
> ......
>
> How to reference the files in "lib" folder in my plan? Should I use "import"
> tag?
>
> I want to package all these files into a single EAR file. Any help would be
> appreciated!
>
> regards,
>
> - Jian Liao