Thanks again for your input. I have just checked in a fix that should resolve many of your problems. The fix allows the user to specify the app server installation directory on the command line and removes the confusing default:
>From now on, to install, do the following:
mvn pluto:install -DinstallDir=path/to/app_server_home
David
On 10/25/05, David H. DeWolf <[EMAIL PROTECTED]> wrote:
Awesome feedback, thanks!!!!! Comments like this will greatly help 1.1 get off the ground floorOn 10/25/05, Graham Klyne < [EMAIL PROTECTED]> wrote:The Pluto 1.1 installation instructions given on the web site [1] are
not working for me. I suspect there's some information missing
concerning specification of the Tomcat installation directory.
The first step (mvn install) runs OK, but the second step has two
problems: (1) the "cd ../pluto-util" doesn't work in the sequence
given; I suspect it should be "cd pluto-util", and (2) using this cd
command, running "mvn pluto:install" fails with a non-existemnt
directory error. A copy of my installation log is below [3].
Correct.
1) Should be 'cd pluto-util'
2) You are correct, the non-existent directory error is a result of not specifying the directory in which tomcat is installed. It defaults to a directory called pluto-tomcat which it assumes is a sibling of the <PLUTO_HOME> dir (probably not ideal, but should it default to something?).
I *think* that maven 2 allows these plugin settings to be overwritten in a users settings.xml file - However, I'm not that far along yet in the development of the install plugin to know for sure. I'll try to get to that ASAP.
Perhaps another approach we could take would be to simply require the user to enter the dir on the command line at execution? Thoughts?
I think the instructions at [1] should explain how to specify the Tomcat
installation directory (by editing pluto-util/pom.xml? see below).
Yes, they should. However, I'm pretty sure that it shouldn't be by modifying the pom. (The pom in maven is used for specifying project scoped information - not for user/system specific properties). Let's figure out a way to move that setting from the pom and let individual users override it either on the command line or in the settings.xml file.
Also, the issue tracking link at [2] is broken.
Woops! Looks like it's not specified in the pom. The correct url is:
http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10560
That's the bare desription, more details follow...
Initially, I was wondering how Maven would know about my tomcat
installation directory. I did a little poking about in the pom.xml
files and came up with:
[[
<configuration>
<installationDirectory>../../pluto-tomcat</installationDirectory>
</configuration>
]]
in pluto-util/pom.xml. Further searching shows references to
${pluto.installation.dir} in file
maven-pluto-plugin/target/classes/META-INF/maven/plugin.xml, which I
take to be where the directory specified above is actually used. (There
are layers of things going on here that I find hard to follow; pointers
to relevant documentation would be helpful.)
Relevant documentation? Your email will help form a lot of it. Thanks for your patience. Feel free to keep on pinging this list for answers. This type of email is very helpful to the community.
So I tried editing the pluto-util/pom.xml to reference my Tomcat
installation directory tree C:/DEV/Apache Software Foundation/Tomcat
5.5/webapps/pluto-tomcat instead of the relative path used previously.
Same error ("Installation Directory C:\DEV\Apache Software
Foundation\Tomcat 5.5\webapps\pluto-tomcat does not exist").
So I create the target directory, and try again. This appears to
succeed. But examination of the files suggeststhat they should have
been installed relative to tomcat root. I delete the files just
installed, change the installation directory to "C:/DEV/Apache Software
Foundation/Tomcat 5.5" and try again. This works, and this time the new
Pluto servlets appear in the tomcat management page.
Correct - it's looking for TOMCAT HOME
Browsing to http://localhost:8080/pluto-testsuite/ gets me a "Hello
world" display. (Now how did I run those test cases previously...?)
The test cases are run through the portal. url should be
http://localhost:8080/pluto/ or localhost:8080/pluto-portal depending on how your context.xml is defined (see previous email).
David
#g
--
[1] http://portals.apache.org/pluto/1.1/getting-started.html
[2] http://portals.apache.org/pluto/1.1/issue-tracking.html
...
[3] Log of attempted installation per [1]
[[
D:\Work\OxfordCS\Pluto-1.1>cd ..\pluto-util
The system cannot find the path specified.
D:\Work\OxfordCS\Pluto-1.1>cd pluto-util
D:\Work\OxfordCS\Pluto-1.1\pluto-util>mvn pluto:install
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'pluto'.
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO]
----------------------------------------------------------------------------
[INFO] Building Pluto
[INFO] task-segment: [pluto:install]
[INFO]
----------------------------------------------------------------------------
[INFO] [pluto:install]
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] Installation Directory
D:\Work\OxfordCS\Pluto-1.1\pluto-util\..\..\pluto-tomcat does not exist.
[INFO]
----------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: 12 seconds
[INFO] Finished at: Tue Oct 25 11:22:11 BST 2005
[INFO] Final Memory: 3M/7M
[INFO]
----------------------------------------------------------------------------
]]
--
Graham Klyne
Research Technology Service
Oxford University Computing Services
