Ian, I am not taking off till Monday morning so I will be available today and tomorrow (Saturday and Sunday) to do some more testing of the build...
Leaving on Monday and back on Monday May 5. Maven can be installed anywhere you want to put it, I put mine in that spot out of my own personal convention... So, to answer your question it is a variable... Part II of your questions I read over the Maven installation notes and there is no requirement to set a MAVEN_HOME.... Unlike Ant, if you read the installation instructions for ant you will note that an ANT_HOME is required So, we can NOT assume that people on Windows systems will have MAVEN_HOME set... Also, from what I can read of your pom.xml the reason you are invoking Ant is to simplify the build process so people don't have to do two things... 1) switch directories to java/server and 2) don't have to type mvn jetty:run or mvn jetty:run-war I am not proposing you do the following but if you did, these are the issues you will have to deal with... If you asked people to set a MAVEN_HOME then Ant has the ability to find maven and execute it... There is a task in Ant that allows one to read environment variables. However, and this is a big however --- In order to run the webapp in debug mode using the Java Platform Debugger Architecture (JPDA) ; which is required for http://cwiki.apache.org/WICKET/maven-jetty-plugin.html The following environment variable has to be set MAVEN_OPTS -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y And when you do this --- then your code doesn't work at all, even with the hard code of the path to Maven I had to uncomment this whole environment variable MAVEN_OPTS in order for the maven to launch as an executable inside Ant... For some reason, and this will require more research and testing, Ant doesn't play well with Maven when these environment variables are set.... Granted, I didn't spend much time trying different options and if someone has time on a Windows box they can play with these environment variables and see if they can get things to work... This is what I was going to do if I had more time before I leave but it will have to wait until I get back in town... There is a new guy working at Webtide -- they are the consulting arm of the Jetty folks and his name is Jesse, he just started working with the Jetty folks a couple of months back and he is an expert on Maven and is helping the Jetty folks come up to speed on developing the whole Maven - Jetty interface better... Here is his blog and contact info... http://blogs.webtide.com/jesse/ I was going to contact him and spend more time understanding the whole plugin architecture of maven as it relates to Jetty -- and ask Jesse some questions on the direction they are going with Jetty and Maven combined... So, in the mean time I would recommend the simple solution for now, and then go for the fancier one on the next round of pom.xml updates... Just have people manually do the following.... 1) Switch to the java/server directory by hand, 2) Execute maven by hand with the mvn jetty:run And then you will be set... Otherwise, talk to Jesse about the environment variables above, or some other person who knows about this topic... This also leads in to the whole issue of Eclipse and how to properly integrate Maven - Eclipse - Jetty and get it all right and simple to use... I have not done any testing with Eclipse at all on this go round... I am simply trying to get our build tested and working at the command line, which has clearly not been an easy task... When I get back in town -- I would also like to address the whole Eclipse issue myself -- and how to do the Jetty Launcher which is a task on the JIRA... I believe this Jesse guy will make some good strides on making Jetty as easy to use in Eclipse as Tomcat currently is... As you know, Tomcat basically comes out of the box in Eclipse and the debugging environment CURRENTLY is much easier with Tomcat/Eclipse than it is with Jetty, especially when you throw the Maven Eclipse plugin into the fray... Enough mumbling, Thanks for all of your work on this topic, Michael I Angerman On Sat, Apr 26, 2008 at 2:54 AM, Ian Boston <[EMAIL PROTECTED]> wrote: > Anyone know if maven is normally installed in the same place on windows, > ie > c:\apache\maven\bin\mvn.bat > > Or is it variable ? > > or... is there any other way of finding the full patch of the executable > eg MAVE_HOME, arg0 > > Ian > > > > > On 26 Apr 2008, at 02:54, Michael Angerman wrote: > > Ian, > > > > Excellent call, that was it -- when I hard coded the path in there the > > jetty > > server comes up and the samples all run fine... > > > > Ian/Cassie > > > > I am heading out of town on Monday morning and will be back the > > following > > Monday May 5. > > > > Will be happy to do more testing on Windows upon my return -- but by > > then > > everything should be working :) > > > > Have fun ! > > Michael I Angerman > > > > > > <exec dir="java/server" > > executable="c:\apache\maven\bin\mvn.bat" failonerror="true" > > > <arg value="jetty:run"/> > > <arg > > value="-DrunType=${runType}"/> > > </exec> > > > > > > On Fri, Apr 25, 2008 at 5:07 PM, Ian Boston <[EMAIL PROTECTED]> wrote: > > > > I have a feeling that this might be a path thing. > > > > > > where it says > > > <exec dir="java/server" executable="mvn" failonerror="true" > > > > <arg value="jetty:run"/> > > > <arg > > > value="-DrunType=${runType}"/> > > > > > > can you try replacing the mvn with the absolute path to your mvn > > > command. > > > Thanks > > > Ian > > > > > > > > > > > > > > > On 25 Apr 2008, at 23:29, Michael Angerman wrote: > > > > > > Embedded error: Execute failed: java.io.IOException: CreateProcess: > > > mvn > > > > > > > jetty:run -DrunType=full error=2 > > > > > > > > > > > > > > >
