1 |
Dave Nebinger wrote: |
2 |
> Okay, so if I have a servlet to deploy to an application container such as |
3 |
> tomcat, is there an eclass that I can use to inherit from? |
4 |
|
5 |
I don't think so. |
6 |
|
7 |
> |
8 |
> Obviously the webapp eclass helps for straight apache-like deployments, but |
9 |
> it's not going to help much when deploying to tomcat. |
10 |
> |
11 |
|
12 |
Well maybe the webapp setup can be configured or added the support for |
13 |
tomcat too. It is just a matter of paths I think. |
14 |
|
15 |
> |
16 |
> I looked in /usr/portage/ebuild, but nothing jumped out at me... |
17 |
> |
18 |
|
19 |
I don't think we have any servlets packaged in the tree at the moment. |
20 |
|
21 |
> |
22 |
> So how do I get my war file deployed? Am I left to external tools such as ant |
23 |
> to manage that for me? |
24 |
> |
25 |
|
26 |
ant is a helper tool for building java software from sources, hopefully |
27 |
no-one uses it for package management. I think at the moment people just |
28 |
do the management manually, but you need to ask people who actually use |
29 |
tomcat in production. |
30 |
|
31 |
> |
32 |
> How does such an entity fit within the portage world? |
33 |
> |
34 |
|
35 |
If we start packaging servlets, then we of course need a setup for that, |
36 |
but it is not something the java team is actively looking into. Feel |
37 |
free to do your own development and we can then integrate it to the |
38 |
official tree if we find it a valuable addition. |
39 |
|
40 |
Regards, |
41 |
Petteri Räty |