1 |
I'm beginning to install and evaluate various Java frameworks, IDEs, |
2 |
and plugins, and would like to write ebuilds for them. Some |
3 |
questions arise: |
4 |
|
5 |
1) Should there be a virtual for servlet containers? At present |
6 |
there are several containers available including tomcat, jetty, and |
7 |
jboss (and that's just open source). I've only worked with tomcat, |
8 |
but some of the references I've read say that each servlet |
9 |
container has its own directory structure and its own way to |
10 |
install servlet-based webapps. When writing an ebuild for a webapp |
11 |
it would be nice to know, in a standard way, whether a container is |
12 |
available and if so, which. |
13 |
|
14 |
It would be even nicer if there was an eclass or portage |
15 |
function for webapp install that would DTRT with whatever container |
16 |
was installed, or if there were functions such as dowar_jetty(), |
17 |
dowar_tomcat3(), dowar_tomcat4(), etc. Or should this functionality |
18 |
be put in a utility, say java_servlet_config, modelled on |
19 |
java_config, for ebuilds to use?) |
20 |
|
21 |
2) Related question: what should the default container dependency be |
22 |
if none is installed? Tomcat? |
23 |
|
24 |
3) Some Java tools, such as Struts Console, can be installed |
25 |
standalone or as a plugin to one or more Java IDE's. Should there |
26 |
be a USE variable for each of the IDE's, that an ebuild can consult |
27 |
to see which IDE's it should install itself into? If so, how would |
28 |
version dependency/compatability issues be handled? |
29 |
|
30 |
If such flags are used, there should also be a |
31 |
"java_tool_standalone" flag to indicate installation as a |
32 |
standalone tool when possible. (Apropos this matter, Oracle just |
33 |
introduced a proposal into the JCP to standardise plugin |
34 |
architecture across IDEs.) |
35 |
|
36 |
Thanks, |
37 |
|
38 |
--Dwight Tuinstra |
39 |
|
40 |
|
41 |
|
42 |
-- |
43 |
gentoo-dev@g.o mailing list |