Wait. That's what I did in the first place and it didn't work. Eric
Jason van Zyl wrote: >On Mon, 2002-07-15 at 16:22, Eric Weidner wrote: > > >>So, if I don't have Maven installed at all, I can use the latest >>distribution to install it and then do a build from cvs (what target? >> build-bootstrap wipes the maven dir) to update to the latest? >> >> > >Just check out the sources from CVS and 'ant -f build-bootstrap.xml' and >when it's finished you'll have a working version of Maven. > > > >>Jason van Zyl wrote: >> >> >> >>>On Mon, 2002-07-15 at 16:00, Eric Weidner wrote: >>> >>> >>> >>> >>>>So, when is your best guess as to when the latest CVS code will be in a >>>>useable state? I'd rather not download the released version because I >>>>hate using old stuff that is effectively obsolete when I download it. :) >>>> >>>>BTW, thanks for the quick reply. >>>> >>>> >>>> >>>> >>>It works now if all you want to do is build. I still don't have the >>>tasklist/changelog/activity reports working but everything else does. >>> >>>Maven itself works. It's a few plugins that don't work yet. If you >>>download and bootstrap you can use Maven, you just can't generate the >>>complete site. >>> >>> >>> >>> >>> >>>>Eric >>>> >>>>Jason van Zyl wrote: >>>> >>>> >>>> >>>> >>>> >>>>>On Mon, 2002-07-15 at 15:48, Eric Weidner wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>I'm having trouble getting Maven to install properly on the latest cvs >>>>>>code. I checkout the latest code and follow the instructions on the >>>>>>site (ant -f build-bootstrap.xml). It seems to install fine where I >>>>>>told it to go (/opt/maven), but if I try to run the maven:jar target >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>from several turbine projects (turbine-3, torque, etc) I get >>>>> >>>>> >>>>> >>>>> >>>>>>"java.io.FileNotFoundException: /opt/maven/plugins/core/build.xml (No >>>>>>such file or directory)". >>>>>> >>>>>>It appears that the installer has neglected to install almost all of the >>>>>>plugin build.xml files. I tried Friday and it did seem to create the >>>>>>plugin/core directory, etc. I tried today and it doesn't even create >>>>>>the core directory now. >>>>>> >>>>>>Same thing applies with the maven:docs target. It seems that the docs >>>>>>on the site are out of synch with the cvs code (understandable since >>>>>>they probably synch with the "realease" version), but I can't build them >>>>>>to see what the new docs would say. >>>>>> >>>>>>This is my first attempt at using Maven. Help!! >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>If this is your first attempt then I suggest you not use CVS HEAD. It >>>>>more than likely will not work for you and you'll get frustrated. We're >>>>>in the middle of the big plugin shakedown so nothing is likely to work >>>>>for you. The docs are out of sync because I haven't been able to deploy >>>>>the site yet with the plugins. But hopefully that will be fixed today. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>Eric Weidner >>>>>> >>>>>> >>>>>>-- >>>>>>To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >>>>>>For additional commands, e-mail: <mailto:[EMAIL PROTECTED] >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >> >>
