Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- E. J. Mansky II Eikonal Research Institute Bend, Oregon - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
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 man...@mindspring.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- E. J. Mansky II Eikonal Research Institute Bend, Oregon - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! dev-h...@maven.apache.org
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
The Apache Software Foundation releases open _source_ products. If one of our users wants to build the product from source, instead of using our convenience binaries, we should be helping, not pushing them to the binaries. On Thu, Nov 7, 2013 at 8:37 AM, Baptiste Mathus m...@batmat.net wrote: 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 man...@mindspring.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- E. J. Mansky II Eikonal Research Institute Bend, Oregon - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
Try adding: mkdir dir=bootstrap/target/classes/META-INF/maven/org.apache.maven/maven-core / before the echo task on line 236 On 7 Nov 2013, at 13:27, Ed Mansky wrote: 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- E. J. Mansky II Eikonal Research Institute Bend, Oregon - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
Well, I agree. I was just pointing that out because that might not actually be what Ed actually wants. I had this fuzzy feeling when reading his mails (and not seing a sentence assertively stating that he didn't want to use the already provided binaries, which is fine in the ASF you're totally right). I was somehow under the impression that Ed might be trying to build Maven because that seemed the only way to use Maven on a PPC architecture or so. But, sure, if Ed is actually trying to build because he wants to use a version he built himself, we can help Cheers 2013/11/7 Benson Margulies bimargul...@gmail.com The Apache Software Foundation releases open _source_ products. If one of our users wants to build the product from source, instead of using our convenience binaries, we should be helping, not pushing them to the binaries. On Thu, Nov 7, 2013 at 8:37 AM, Baptiste Mathus m...@batmat.net wrote: 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 man...@mindspring.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- E. J. Mansky II Eikonal Research Institute Bend, Oregon - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
PS. note that JUnit is only required by the Ant tests, you can build a minimal distribution of Ant by removing the test-jar dependency from dist-lite and running: ant dist-lite Alternatively if you want to run the Ant unit tests for sanity checking, you can always build a basic JUnit4 distribution with Ant 1.6.5 (it still comes with a build.xml) On 7 Nov 2013, at 14:22, Stuart McCulloch wrote: Try adding: mkdir dir=bootstrap/target/classes/META-INF/maven/org.apache.maven/maven-core / before the echo task on line 236 On 7 Nov 2013, at 13:27, Ed Mansky wrote: 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- E. J. Mansky II Eikonal Research Institute Bend, Oregon - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
Hi, Yes, I tried to use the binaries first, but on the ppc architecture when I type mvn -version I see: Exception in thread main java.lang.NoClassDefFoundError: org/codehaus/plexus/classworlds/launcher/Launcher. I get this for Maven version 3.1.1 What I am trying to do is install the newer versions of the JDK on my ppc machine. On Tiger the last Apple-supplied JDK is 1.5 So I am trying to install JDK 1.6 on the way to installing 1.7 ultimately. The SoyLatte work of Landon Fuller and others is for the Intel-based chipset only. Hence my interest in building from source code for the ppc. I found that to build a new version of Ant I needed JUnit. JUnit in turn requires Maven. My apologies if this is not the correct mailing list, I thought it might be since my questions were specific to the build requirements and underlying build scripts used to build and install Maven. I see some mention on other blogs of using the Surefire plugin to get around the need for Maven 3 when using JUnit 4. Can one use the Surefire plugin to build Junit 4 with only Maven 2 installed? Alternatively, to install Maven 3.x with Maven 2.x installed already, are there other XML libraries I need to get that echo task w/encoding to be correctly executed in the build.xml file for maven 3.x ? Because otherwise the requirements for Maven 3.x lead to Ant 1.8+ which in turn lead to JUnit 4 (I think) and that leads back to Maven 3.x --hence my difficulty. And thanks Stuart for pointing out that one can tell ant to skip the junit tests when building. I will try that as well. --Ed 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 man...@mindspring.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
I'd step back and try Maven 3.0.5's binaries... I am beginning to wonder if a Java 6 dependency crept into 3.1.x On 7 November 2013 15:05, Ed Mansky man...@mindspring.com wrote: Hi, Yes, I tried to use the binaries first, but on the ppc architecture when I type mvn -version I see: Exception in thread main java.lang.NoClassDefFoundError: org/codehaus/plexus/classworlds/launcher/Launcher. I get this for Maven version 3.1.1 What I am trying to do is install the newer versions of the JDK on my ppc machine. On Tiger the last Apple-supplied JDK is 1.5 So I am trying to install JDK 1.6 on the way to installing 1.7 ultimately. The SoyLatte work of Landon Fuller and others is for the Intel-based chipset only. Hence my interest in building from source code for the ppc. I found that to build a new version of Ant I needed JUnit. JUnit in turn requires Maven. My apologies if this is not the correct mailing list, I thought it might be since my questions were specific to the build requirements and underlying build scripts used to build and install Maven. I see some mention on other blogs of using the Surefire plugin to get around the need for Maven 3 when using JUnit 4. Can one use the Surefire plugin to build Junit 4 with only Maven 2 installed? Alternatively, to install Maven 3.x with Maven 2.x installed already, are there other XML libraries I need to get that echo task w/encoding to be correctly executed in the build.xml file for maven 3.x ? Because otherwise the requirements for Maven 3.x lead to Ant 1.8+ which in turn lead to JUnit 4 (I think) and that leads back to Maven 3.x --hence my difficulty. And thanks Stuart for pointing out that one can tell ant to skip the junit tests when building. I will try that as well. --Ed 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 man...@mindspring.com 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: dev-unsubscr...@maven.apache.org
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
I'd try to unset M2_HOME and/or MAVEN_HOME. Seems like the typical error you get when you set that variable pointing to another maven version than the one you're currently trying to run. Most often I just advise to get simply get rid of its use anywhere. Maven actually doesn't need it and finds its root by itself. Cheers Le 7 nov. 2013 16:06, Ed Mansky man...@mindspring.com a écrit : Hi, Yes, I tried to use the binaries first, but on the ppc architecture when I type mvn -version I see: Exception in thread main java.lang.NoClassDefFoundError: org/codehaus/plexus/classworlds/launcher/Launcher. I get this for Maven version 3.1.1 What I am trying to do is install the newer versions of the JDK on my ppc machine. On Tiger the last Apple-supplied JDK is 1.5 So I am trying to install JDK 1.6 on the way to installing 1.7 ultimately. The SoyLatte work of Landon Fuller and others is for the Intel-based chipset only. Hence my interest in building from source code for the ppc. I found that to build a new version of Ant I needed JUnit. JUnit in turn requires Maven. My apologies if this is not the correct mailing list, I thought it might be since my questions were specific to the build requirements and underlying build scripts used to build and install Maven. I see some mention on other blogs of using the Surefire plugin to get around the need for Maven 3 when using JUnit 4. Can one use the Surefire plugin to build Junit 4 with only Maven 2 installed? Alternatively, to install Maven 3.x with Maven 2.x installed already, are there other XML libraries I need to get that echo task w/encoding to be correctly executed in the build.xml file for maven 3.x ? Because otherwise the requirements for Maven 3.x lead to Ant 1.8+ which in turn lead to JUnit 4 (I think) and that leads back to Maven 3.x --hence my difficulty. And thanks Stuart for pointing out that one can tell ant to skip the junit tests when building. I will try that as well. --Ed 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 man...@mindspring.com 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,
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
You can't *install* Maven from the source code, only build it. Why do you need to build Maven from source? If you want to install Maven you should download the official distro: http://maven.apache.org/download.cgi /Anders On Wed, Nov 6, 2013 at 3:36 PM, Ed Mansky man...@mindspring.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Install question for Maven 3.0 on PPC/10.4.11/ant 1.6.5
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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
