On 11/3/05, Pollähne. Ullrich <[EMAIL PROTECTED]> wrote:
I haven't figured out a good solution for this yet. If you have any ideas, chime in. Here's my dilema:
1) I Iike the artifact names of pluto-testsuite, pluto-container, pluto-xxxx, etc. . .because generic artifact names can easily conflict with other projects.
2) In order to allow this but also allow simple context paths, pluto deploys the war and uses tomcat context configuration to bind the war to another context path.
3) Tomcat, by default, unpacks all wars, meaning that pluto-testsuite.war is unpacked to a directory named after it's context path -- /testsuite
4) Tomcat, also by default, auto deploys all wars in the webapps dir. This results in pluto-testsuite.war being deployed to /pluto-testsuite
So, the end result is what you're seeing.
Another approach would be to point the context configuration a wars that are NOT in the webapps dir. This may be the best approach but I'm not sure where we'd place the war. Should we leave it in the target dir? move it to another subdir of tomcat? etc. . .
Any ideas?
Hi David,thanks for the fast response.>Tomcat 5.5.9 works fine.Yes, tomcat.5.5.9 is really completely different. ;-)It creates pluto, pluto-portal, testsuite and pluto-testsuite. Is it planned to remove this duplicity?
I haven't figured out a good solution for this yet. If you have any ideas, chime in. Here's my dilema:
1) I Iike the artifact names of pluto-testsuite, pluto-container, pluto-xxxx, etc. . .because generic artifact names can easily conflict with other projects.
2) In order to allow this but also allow simple context paths, pluto deploys the war and uses tomcat context configuration to bind the war to another context path.
3) Tomcat, by default, unpacks all wars, meaning that pluto-testsuite.war is unpacked to a directory named after it's context path -- /testsuite
4) Tomcat, also by default, auto deploys all wars in the webapps dir. This results in pluto-testsuite.war being deployed to /pluto-testsuite
So, the end result is what you're seeing.
Another approach would be to point the context configuration a wars that are NOT in the webapps dir. This may be the best approach but I'm not sure where we'd place the war. Should we leave it in the target dir? move it to another subdir of tomcat? etc. . .
Any ideas?
>Make sure you do it from pluto-utilAfter getting the latest changes I will try again (I did execute the task in pluto-util).Ullrich.
