Hi, I'm under the impression this question should have actually been asked on the user ML. You seem to be trying to build Maven although you shouldn't have to do.
So, what are you actually trying to achieve currently? Maven is a pure Java tool, so unless you're actually trying to hack on Maven itself (which would mean I was wrong and you're writing to the right list), you can use stock maven binaries available from the maven website. As you're already able to run Ant, which is also pure Java, Maven would run fine too (nothing architecture/OS specific). HTH Cheers 2013/11/7 Ed Mansky <[email protected]> > I saw the requirement for Ant 1.8 or later. The encoding option in the > echo task is new since Ant 1.7. > > To install ant 1.7, 1.8 or 1.8.4 requires JUnit to already be present. > Unfortunately, to build JUnit you need maven in place. > > Hence my attempt to install/build maven. > > I found that I was able to build and install maven version 2.2.1 fine on > Tiger/ppc. > > Apparently there have been a lot of changes in the build.xml file between > 2.2.1 and 3.x versions of maven. > > Now, typing "mv install" in the Junit folder results in "Unable to build > project ...junit/pom.xml; it requires Maven version 3.0.4" > > which is a different issue involving building junit 4 with maven 2. > > --Ed > > > > > The README.bootstrap.txt from the source tree states the pre-requisites >> for building the bootstrap code are: >> >> - Java 1.5 >> - Ant 1.8 or later >> >> Whereas you're using Ant 1.6.5 - this is likely the problem, because >> 1.6.5 doesn't support the use of an encoding in the echo task (this is what >> creates that particular pom.properties file) >> >> On 6 Nov 2013, at 14:36, Ed Mansky wrote: >> >> Hi all, >>> >>> I am trying to install Maven from source code on a PowerMac G4 PPC 7450 >>> running 10.4.11 and with >>> Java JDK 1.5 and Ant 1.6.5 installed. >>> >>> I am getting an error from line #236 of build.xml >>> (java.io.FileNotFoundException: >>> ...full path to pom.properties file) >>> >>> Apparently the pom.properties file that is expected to be the bootstrap >>> area for that target (compile-boot) to run, is missing. >>> >>> The missing file "pom.properties" is indeed located in the source code >>> tree in: >>> >>> maven-core/src/test/resources/META-INF/maven/org.apache. >>> maven/maven-core >>> >>> I am new to Maven, but it appears that an entry in >>> maven-core/src/main/mdo/toolchains.mdo for this file in META-INF is >>> needed in order to get it copied over to the bootstrap area during the >>> building of the target "generate-sources". >>> >>> My environment variables are set as follows: >>> >>> JAVA_HOME = /Library/Java/Home >>> ANT_HOME = /Developer/Java/Ant >>> M2_HOME = /usr/local/maven-3.0.4 >>> >>> I also set M3_HOME = /usr/local/maven-3.0.4 in case that was needed >>> instead of M2_HOME >>> >>> I do not have CLASSPATH defined at all. >>> >>> What am I missing here to get Maven to build? Any tips or hints would >>> be greatly appreciated! >>> >>> Thanks, >>> >>> --Ed >>> -- >>> E. J. Mansky II >>> Eikonal Research Institute >>> Bend, Oregon >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > -- > E. J. Mansky II > Eikonal Research Institute > Bend, Oregon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! nbsp;! <[email protected]> >
