Re: Strange Issue
Hi Ole and Mark, I ran into a similar problem before, what I did to resolve the issue is I ran 'mvn -version' to see what Maven "thought" it was using for a JDK, then I investigated the Eclipse settings to see if it was using the same exact JDK - you may need to point the Java configuration to a JDK (install one if you haven't done so already). The other point to look at is to see whether the Maven runtime Eclipse is using is the embedded plugin or some other plugin, I tend to point the Eclipse mvn executable to my command-line install. -L- On Wed, Dec 31, 2014 at 9:52 AM, Ole Ersoy wrote: > Hi Mark, > > I do have Open JDK installed. The reason this is strange is because the > maven build runs fine from the command line after the project is run with > Eclipse. Other maven builds I have also run fine from the command line. > For example if I git clone apache commons math and run the build, it builds > fine. > > In this case I'm just creating a very minimal project with: > - pom.xml > - src/test/java/hello/HelloTest.java > > When I try to run the build, it fails. If I import it into eclipse, it > runs. When I try the build from the command line again, it runs. If I > create another project with the same set of original resources, it fails > all over again. > > Thoughts? > > Thanks again, > Ole > > > > On 12/31/2014 11:17 AM, Mark Eggers wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 12/31/2014 8:49 AM, Ole Ersoy wrote: >> >>> Hi, >>> >>> I'm seeing some strange behavior with Maven 3.0.5 on Ubuntu. >>> >>> BACKGROUND = When I run `mvn test` the console >>> prints: `[ERROR] No compiler is provided in this environment. >>> Perhaps you are running on a JRE rather than a JDK?` >>> >>> If I then open the project in Eclipse and run the test it runs >>> fine. Subsequently if I close Eclipse and run the test with `mvn >>> test` I get `BUILD SUCCESS`. >>> >>> ANALYSIS = I run `mvn test` on the `test2` >>> project, that was opened with eclipse, and I get -> `BUILD >>> SUCCESS`. >>> >>> I then create a `test3` project, copy the pom and the src directory >>> from test2 to test 3. When running `mvn test` on the `test3` >>> project I get the error again. I included the result from my >>> console below: >>> >>> ole@MKI:~/test2$ mvn test Warning: JAVA_HOME environment variable >>> is not set. [INFO] Scanning for projects... [INFO] [INFO] >>> >>> >>> >>> [INFO] Building test-maven 1.0.0 >> >>> [INFO] >>> >>> >>> >>> [INFO] >> >>> [INFO] --- maven-resources-plugin:2.3:resources (default-resources) >>> @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) >>> to copy filtered resources, i.e. build is platform dependent! >>> [INFO] skip non existing resourceDirectory >>> /home/ole/test2/src/main/resources [INFO] [INFO] --- >>> maven-compiler-plugin:3.2:compile (default-compile) @ test-maven >>> --- [INFO] No sources to compile [INFO] [INFO] --- >>> maven-resources-plugin:2.3:testResources (default-testResources) @ >>> test-maven --- [WARNING] Using platform encoding (UTF-8 actually) >>> to copy filtered resources, i.e. build is platform dependent! >>> [INFO] skip non existing resourceDirectory >>> /home/ole/test2/src/test/resources [INFO] [INFO] --- >>> maven-compiler-plugin:3.2:testCompile (default-testCompile) @ >>> test-maven --- [INFO] Nothing to compile - all classes are up to >>> date [INFO] [INFO] --- maven-surefire-plugin:2.10:test >>> (default-test) @ test-maven --- [INFO] Surefire report directory: >>> /home/ole/test2/target/surefire-reports >>> >>> --- T E S T S >>> --- Running >>> hello.HelloUnitTest Greeting from hello the Unit Test! Tests run: >>> 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.039 sec >>> >>> Results : >>> >>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 >>> >>> [INFO] >>> >>> >>> >>> [INFO] BUILD SUCCESS >> >>> [INFO] >>> >>> >>> >>> [INFO] Total time: 1.027s >> >>> [INFO] Finished at: Wed Dec 31 10:41:25 CST 2014 [INFO] Final >>> Memory: 8M/240M [INFO] >>> >>> >>> >>> ole@MKI:~/test2$ mkdir ../test3 >> >>> ole@MKI:~/test2$ cp pom.xml ../test3 ole@MKI:~/test2$ cp -r src >>> ../test3 ole@MKI:~/test2$ cd ../test3/ ole@MKI:~/test3$ mvn test >>> Warning: JAVA_HOME environment variable is not set. [INFO] Scanning >>> for projects... [INFO] [INFO] >>> >>> >>> >>> [INFO] Building test-maven 1.0.0 >> >>> [INFO] >>>
Re: Strange Issue
Am Wed, 31 Dec 2014 14:09:39 -0600 schrieb Ole Ersoy : > Thanks!! You were right all along. I just did a fresh install on my > machine, and all my other builds were running fine, so I thought the > entire JDK had been pulled in by one of my dependencies. Once I did > a `mvn clean` on these builds, they also stopped building. BTW: maven does not "pull in the JDK". The reason why it builds with Eclipse is, it has its own compiler and does not need a JDK (for this). And when command-line maven sees compiled classes which are newer than the java source, it will not try to compile them. So only if your target directory is empty or a java file was modified after comile maven will try to start the compiler (from the JDK). Most other stuff works with only a JRE. Gruss Bernd - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange Issue
Hello, is there a directory /usr/lib/jvm/java-7-openjdk-amd64/include/? If not, this is not the JDK but the JRE version. http://packages.ubuntu.com/en/precise/amd64/openjdk-7-jre/filelist http://packages.ubuntu.com/en/precise/amd64/openjdk-7-jdk/filelist In that case it will help to install openjdk-7-jdk package. It is quite possible that you do not have any JDK on your machine, if you do not, it will help to install openjdk-7-jdk. If you do have one, you need to find it and set JAVA_HOME to it. This will not only resolve your problem, but also remove the warning :) Gruss Bernd Am Wed, 31 Dec 2014 13:09:33 -0600 schrieb Ole Ersoy : > Bernd, Mark, > > Here is the result of `mvn --version`: > Apache Maven 3.0.5 > Maven home: /usr/share/maven > Java version: 1.7.0_65, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.13.0-43-generic", arch: "amd64", > family: "unix" - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange Issue
Bernd, Mark, Here is the result of `mvn --version`: Apache Maven 3.0.5 Maven home: /usr/share/maven Java version: 1.7.0_65, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-43-generic", arch: "amd64", family: "unix" This is the project structure: ole@MKI:~/test2$ tree . ├── pom.xml └── src └── test └── java └── hello └── HelloUnitTest.java 4 directories, 2 files Sequence: - `mvn clean` - Now the compilation error occurs. - Import the project into eclipse - Run the test. It runs fine. - Try 'mvn test' - Runs fine - Run `mvn clean` - Run `mvn test` - Compilation error Here's a dump of my terminal: ole@MKI:~/test2$ mvn clean Warning: JAVA_HOME environment variable is not set. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building test-maven 1.0.0 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ test-maven --- [INFO] Deleting /home/ole/test2/target [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 0.635s [INFO] Finished at: Wed Dec 31 12:39:57 CST 2014 [INFO] Final Memory: 6M/240M [INFO] ole@MKI:~/test2$ mvn test Warning: JAVA_HOME environment variable is not set. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building test-maven 1.0.0 [INFO] [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test2/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ test-maven --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.3:testResources (default-testResources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test2/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ test-maven --- [INFO] Changes detected - recompiling the module! [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent! [INFO] Compiling 1 source file to /home/ole/test2/target/test-classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? [INFO] 1 error [INFO] - [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.958s [INFO] Finished at: Wed Dec 31 12:40:06 CST 2014 [INFO] Final Memory: 7M/240M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:testCompile (default-testCompile) on project test-maven: Compilation failure [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException ole@MKI:~/test2$ === RUN TEST WITH ECLIPSE - THEN TERMINAL === ole@MKI:~/test2$ mvn test Warning: JAVA_HOME environment variable is not set. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building test-maven 1.0.0 [INFO] [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test2/src/main/resources [INFO] [INFO] --- maven
Re: Strange Issue
Hello, you can use "mvn -version" to see which java is used. Gruss Bernd Am Wed, 31 Dec 2014 10:23:00 -0800 schrieb Mark Eggers : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Ole, > > In one instance (have to check your mail again) there were no files to > compile, so nothing bad happened. > > If you run mvn clean test, then the target directory will be removed > and Maven will be forced to recompile everything. > > You should get the command line failure consistently then. > > - From your log that you posted: > > Warning: JAVA_HOME environment variable is not set. > > Also, can you run the following from the command line and see if it > works? > > javac -version > > You should get the version of javac echoed. If not, you have a path > problem. > > If you do, run the following command: > > which javac > > This should tell you where javac is installed. I don't know how > alternatives / OpenJDK gets installed on Ubuntu (I use Fedora and > Oracle's JDK), so I don't know if setting JAVA_HOME to javac's parent > directory is appropriate. > > For example, on my system 'which javac' results in: > > /usr/java/bin/javac > > This means that javac is in /usr/java/bin, and the parent directory > (/usr/java) is the value that JAVA_HOME is set to on my system. This > is actually a link to where the current version of Java is installed > on my system. > > One of these days I'll walk through alternatives and figure out if it > meets my needs (or if I should file bug reports). > > . . . just my two cents > /mde/ > > On 12/31/2014 9:52 AM, Ole Ersoy wrote: > > Hi Mark, > > > > I do have Open JDK installed. The reason this is strange is > > because the maven build runs fine from the command line after the > > project is run with Eclipse. Other maven builds I have also run > > fine from the command line. For example if I git clone apache > > commons math and run the build, it builds fine. > > > > In this case I'm just creating a very minimal project with: - > > pom.xml - src/test/java/hello/HelloTest.java > > > > When I try to run the build, it fails. If I import it into > > eclipse, it runs. When I try the build from the command line > > again, it runs. If I create another project with the same set of > > original resources, it fails all over again. > > > > Thoughts? > > > > Thanks again, Ole > > > > > > > > On 12/31/2014 11:17 AM, Mark Eggers wrote: On 12/31/2014 8:49 AM, > > Ole Ersoy wrote: > Hi, > > I'm seeing some strange behavior with Maven 3.0.5 on Ubuntu. > > BACKGROUND = When I run `mvn test` the > console prints: `[ERROR] No compiler is provided in this > environment. Perhaps you are running on a JRE rather than a > JDK?` > > If I then open the project in Eclipse and run the test it > runs fine. Subsequently if I close Eclipse and run the test > with `mvn test` I get `BUILD SUCCESS`. > > ANALYSIS = I run `mvn test` on the > `test2` project, that was opened with eclipse, and I get -> > `BUILD SUCCESS`. > > I then create a `test3` project, copy the pom and the src > directory from test2 to test 3. When running `mvn test` on > the `test3` project I get the error again. I included the > result from my console below: > > ole@MKI:~/test2$ mvn test Warning: JAVA_HOME environment > variable is not set. [INFO] Scanning for projects... [INFO] > [INFO] > > > > > > > [INFO] Building test-maven 1.0.0 > [INFO] > > > > > > > [INFO] > [INFO] --- maven-resources-plugin:2.3:resources > (default-resources) @ test-maven --- [WARNING] Using platform > encoding (UTF-8 actually) to copy filtered resources, i.e. > build is platform dependent! [INFO] skip non existing > resourceDirectory /home/ole/test2/src/main/resources [INFO] > [INFO] --- maven-compiler-plugin:3.2:compile > (default-compile) @ test-maven --- [INFO] No sources to > compile [INFO] [INFO] --- > maven-resources-plugin:2.3:testResources > (default-testResources) @ test-maven --- [WARNING] Using > platform encoding (UTF-8 actually) to copy filtered > resources, i.e. build is platform dependent! [INFO] skip non > existing resourceDirectory /home/ole/test2/src/test/resources > [INFO] [INFO] --- maven-compiler-plugin:3.2:testCompile > (default-testCompile) @ test-maven --- [INFO] Nothing to > compile - all classes are up to date [INFO] [INFO] --- > maven-surefire-plugin:2.10:test (default-test) @ test-maven > --- [INFO] Surefire report directory: > /home/ole/test2/target/surefire-reports > > --- T E S > T S ---
Re: Strange Issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ole, In one instance (have to check your mail again) there were no files to compile, so nothing bad happened. If you run mvn clean test, then the target directory will be removed and Maven will be forced to recompile everything. You should get the command line failure consistently then. - From your log that you posted: Warning: JAVA_HOME environment variable is not set. Also, can you run the following from the command line and see if it works? javac -version You should get the version of javac echoed. If not, you have a path problem. If you do, run the following command: which javac This should tell you where javac is installed. I don't know how alternatives / OpenJDK gets installed on Ubuntu (I use Fedora and Oracle's JDK), so I don't know if setting JAVA_HOME to javac's parent directory is appropriate. For example, on my system 'which javac' results in: /usr/java/bin/javac This means that javac is in /usr/java/bin, and the parent directory (/usr/java) is the value that JAVA_HOME is set to on my system. This is actually a link to where the current version of Java is installed on my system. One of these days I'll walk through alternatives and figure out if it meets my needs (or if I should file bug reports). . . . just my two cents /mde/ On 12/31/2014 9:52 AM, Ole Ersoy wrote: > Hi Mark, > > I do have Open JDK installed. The reason this is strange is > because the maven build runs fine from the command line after the > project is run with Eclipse. Other maven builds I have also run > fine from the command line. For example if I git clone apache > commons math and run the build, it builds fine. > > In this case I'm just creating a very minimal project with: - > pom.xml - src/test/java/hello/HelloTest.java > > When I try to run the build, it fails. If I import it into > eclipse, it runs. When I try the build from the command line > again, it runs. If I create another project with the same set of > original resources, it fails all over again. > > Thoughts? > > Thanks again, Ole > > > > On 12/31/2014 11:17 AM, Mark Eggers wrote: On 12/31/2014 8:49 AM, > Ole Ersoy wrote: Hi, I'm seeing some strange behavior with Maven 3.0.5 on Ubuntu. BACKGROUND = When I run `mvn test` the console prints: `[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?` If I then open the project in Eclipse and run the test it runs fine. Subsequently if I close Eclipse and run the test with `mvn test` I get `BUILD SUCCESS`. ANALYSIS = I run `mvn test` on the `test2` project, that was opened with eclipse, and I get -> `BUILD SUCCESS`. I then create a `test3` project, copy the pom and the src directory from test2 to test 3. When running `mvn test` on the `test3` project I get the error again. I included the result from my console below: ole@MKI:~/test2$ mvn test Warning: JAVA_HOME environment variable is not set. [INFO] Scanning for projects... [INFO] [INFO] > [INFO] Building test-maven 1.0.0 [INFO] > [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test2/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ test-maven --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.3:testResources (default-testResources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test2/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ test-maven --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ test-maven --- [INFO] Surefire report directory: /home/ole/test2/target/surefire-reports --- T E S T S --- Running hello.HelloUnitTest Greeting from hello the Unit Test! Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.039 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] > [I
Re: Strange Issue
Hi Mark, I do have Open JDK installed. The reason this is strange is because the maven build runs fine from the command line after the project is run with Eclipse. Other maven builds I have also run fine from the command line. For example if I git clone apache commons math and run the build, it builds fine. In this case I'm just creating a very minimal project with: - pom.xml - src/test/java/hello/HelloTest.java When I try to run the build, it fails. If I import it into eclipse, it runs. When I try the build from the command line again, it runs. If I create another project with the same set of original resources, it fails all over again. Thoughts? Thanks again, Ole On 12/31/2014 11:17 AM, Mark Eggers wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/31/2014 8:49 AM, Ole Ersoy wrote: Hi, I'm seeing some strange behavior with Maven 3.0.5 on Ubuntu. BACKGROUND = When I run `mvn test` the console prints: `[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?` If I then open the project in Eclipse and run the test it runs fine. Subsequently if I close Eclipse and run the test with `mvn test` I get `BUILD SUCCESS`. ANALYSIS = I run `mvn test` on the `test2` project, that was opened with eclipse, and I get -> `BUILD SUCCESS`. I then create a `test3` project, copy the pom and the src directory from test2 to test 3. When running `mvn test` on the `test3` project I get the error again. I included the result from my console below: ole@MKI:~/test2$ mvn test Warning: JAVA_HOME environment variable is not set. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building test-maven 1.0.0 [INFO] [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test2/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ test-maven --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.3:testResources (default-testResources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test2/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ test-maven --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ test-maven --- [INFO] Surefire report directory: /home/ole/test2/target/surefire-reports --- T E S T S --- Running hello.HelloUnitTest Greeting from hello the Unit Test! Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.039 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1.027s [INFO] Finished at: Wed Dec 31 10:41:25 CST 2014 [INFO] Final Memory: 8M/240M [INFO] ole@MKI:~/test2$ mkdir ../test3 ole@MKI:~/test2$ cp pom.xml ../test3 ole@MKI:~/test2$ cp -r src ../test3 ole@MKI:~/test2$ cd ../test3/ ole@MKI:~/test3$ mvn test Warning: JAVA_HOME environment variable is not set. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building test-maven 1.0.0 [INFO] [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test3/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ test-maven --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.3:testResources (default-testResources) @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /home/ole/test3/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ test-maven --- [INFO] Changes detected - recompiling the module! [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent! [INFO] Compiling
Re: Strange Issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/31/2014 8:49 AM, Ole Ersoy wrote: > Hi, > > I'm seeing some strange behavior with Maven 3.0.5 on Ubuntu. > > BACKGROUND = When I run `mvn test` the console > prints: `[ERROR] No compiler is provided in this environment. > Perhaps you are running on a JRE rather than a JDK?` > > If I then open the project in Eclipse and run the test it runs > fine. Subsequently if I close Eclipse and run the test with `mvn > test` I get `BUILD SUCCESS`. > > ANALYSIS = I run `mvn test` on the `test2` > project, that was opened with eclipse, and I get -> `BUILD > SUCCESS`. > > I then create a `test3` project, copy the pom and the src directory > from test2 to test 3. When running `mvn test` on the `test3` > project I get the error again. I included the result from my > console below: > > ole@MKI:~/test2$ mvn test Warning: JAVA_HOME environment variable > is not set. [INFO] Scanning for projects... [INFO] [INFO] > > > [INFO] Building test-maven 1.0.0 > [INFO] > > > [INFO] > [INFO] --- maven-resources-plugin:2.3:resources (default-resources) > @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) > to copy filtered resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory > /home/ole/test2/src/main/resources [INFO] [INFO] --- > maven-compiler-plugin:3.2:compile (default-compile) @ test-maven > --- [INFO] No sources to compile [INFO] [INFO] --- > maven-resources-plugin:2.3:testResources (default-testResources) @ > test-maven --- [WARNING] Using platform encoding (UTF-8 actually) > to copy filtered resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory > /home/ole/test2/src/test/resources [INFO] [INFO] --- > maven-compiler-plugin:3.2:testCompile (default-testCompile) @ > test-maven --- [INFO] Nothing to compile - all classes are up to > date [INFO] [INFO] --- maven-surefire-plugin:2.10:test > (default-test) @ test-maven --- [INFO] Surefire report directory: > /home/ole/test2/target/surefire-reports > > --- T E S T S > --- Running > hello.HelloUnitTest Greeting from hello the Unit Test! Tests run: > 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.039 sec > > Results : > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > > [INFO] > > > [INFO] BUILD SUCCESS > [INFO] > > > [INFO] Total time: 1.027s > [INFO] Finished at: Wed Dec 31 10:41:25 CST 2014 [INFO] Final > Memory: 8M/240M [INFO] > > > ole@MKI:~/test2$ mkdir ../test3 > ole@MKI:~/test2$ cp pom.xml ../test3 ole@MKI:~/test2$ cp -r src > ../test3 ole@MKI:~/test2$ cd ../test3/ ole@MKI:~/test3$ mvn test > Warning: JAVA_HOME environment variable is not set. [INFO] Scanning > for projects... [INFO] [INFO] > > > [INFO] Building test-maven 1.0.0 > [INFO] > > > [INFO] > [INFO] --- maven-resources-plugin:2.3:resources (default-resources) > @ test-maven --- [WARNING] Using platform encoding (UTF-8 actually) > to copy filtered resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory > /home/ole/test3/src/main/resources [INFO] [INFO] --- > maven-compiler-plugin:3.2:compile (default-compile) @ test-maven > --- [INFO] No sources to compile [INFO] [INFO] --- > maven-resources-plugin:2.3:testResources (default-testResources) @ > test-maven --- [WARNING] Using platform encoding (UTF-8 actually) > to copy filtered resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory > /home/ole/test3/src/test/resources [INFO] [INFO] --- > maven-compiler-plugin:3.2:testCompile (default-testCompile) @ > test-maven --- [INFO] Changes detected - recompiling the module! > [WARNING] File encoding has not been set, using platform encoding > UTF-8, i.e. build is platform dependent! [INFO] Compiling 1 source > file to /home/ole/test3/target/test-classes [INFO] > - > [ERROR] COMPILATION ERROR : [INFO] > - > [ERROR] No compiler is provided in this environment. Perhaps you > are running on a JRE rather than a JDK? [INFO] 1 error [INFO] > - > [INFO] > > > [INFO] BUILD FAILURE > [INFO]
Re: Strange issue with generated jars
On Wed, 13 Nov 2013 15:52:02 -0700 Doug Douglass wrote: > I ran the sample project on a couple systems with different results. > ... > > So it appears to be JDK bug. Thanks. Looks like I'll be taking this up with the OpenJDK people. M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange issue with generated jars
Hi Curtis,
I apologize, I had not recognized that you were not the OP.
"If you just look at it, you can see that it doesn't do anything bad."
- You are correct, I did not bother to download it as it was presented
as being a project with several thousand classes. Perhaps in the
future I should download such things.
On Wed, Nov 13, 2013 at 2:32 PM, Curtis Rueden wrote:
> Hi,
>
> org.apache.maven.u...@io7m.com wrote:
>> Can anyone else reproduce this problem?
>
> OK, I ran the example ("mvn clean package") and the project builds
> successfully on my system:
>
> $ mvn -v
> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
> 10:22:22-0500)
> Maven home: /usr/local/Cellar/maven/3.1.1/libexec
> Java version: 1.7.0_45, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9", arch: "x86_64", family: "mac"
>
> $ jar tf code/target/code-0.1.0.jar |wc
> 11 11 270
>
> $ jar tf resources/target/resources-0.1.0.jar |wc
>65547 65547 2151861
>
> George Wilson wrote:
>> the restriction is in regards to building a larger project like a
>> maven build.
>
> Well, it's 38 lines of code:
>
> $ find . -name '*.java' | xargs wc
> 10 18 157 ./code/src/main/java/com/io7m/jarbug/Main.java
> 28 74 694
> ./resources/src/main/java/com/io7m/jarbug/MakeSources.java
> 38 92 851 total
>
> If you just look at it, you can see that it doesn't do anything bad.
>
>> I am not sure that it is really necessary to ask people to go out of
>> their way to build VM systems
>
> I am not the OP, and was not asking you to do anything. I was merely
> inquiring whether you could perhaps avoid your company's bureaucracy via
> some technical means.
>
>> It seems that since you have run this and generated errors, it would
>> be easier as a first step diagnostic to post your error messages-
>> output cleaned if need be of course.
>
> I agree that it wouldn't hurt for the OP to post his error messages, too.
> But that said, IMHO, posting a complete example project demonstrating the
> issue is about the *best* thing you can do.
>
> Regards,
> Curtis
>
>
> On Wed, Nov 13, 2013 at 4:16 PM, George Wilson wrote:
>
>> A crippling restriction or not, it is company policy which I do not
>> have any authority over. Its one thing to try a snippet from stack
>> overflow but the restriction is in regards to building a larger
>> project like a maven build. The concern is not being able to evaluate
>> what the code or individual scripts do.
>> I do not have time right this minute to set up a VM instance but
>> perhaps could later on workload permitting. It seems that since you
>> have run this and generated errors, it would be easier as a first step
>> diagnostic to post your error messages- output cleaned if need be of
>> course. FWIW, I am not sure that it is really necessary to ask people
>> to go out of their way to build VM systems, when the error output
>> might solve the problem immediately.
>>
>> On Wed, Nov 13, 2013 at 11:37 AM, Curtis Rueden wrote:
>> > Hi George,
>> >
>> > That's a new one on me. Can you build in an isolated VM? On a personal
>> > machine while at work? Not being able to try out code from the Internet
>> > seems like a crippling restriction to me.
>> >
>> > -Curtis
>> > On Nov 13, 2013 1:34 PM, "George Wilson" wrote:
>> >
>> >> Unfortunately, my company's security policies do not allow for the
>> >> downloading and building of external projects without approval from IT
>> >> and security so I cannot really test your code (not without going to a
>> >> committee, etc...). Any chance you can post the errors you are
>> >> getting? Is this a JVM heap issue perhaps? Have you tried increasing
>> >> your Java memory? Just a thought since you mentioned that javac is
>> >> what seems to die here.
>> >>
>> >> On Wed, Nov 13, 2013 at 5:57 AM,
>> wrote:
>> >> > On Tue, 12 Nov 2013 13:02:46 +
>> >> > wrote:
>> >> >
>> >> >> Hello.
>> >> >>
>> >> >> I've run into a strange but easily reproduced problem with the jar
>> files
>> >> >> generated by Maven. Essentially, if I generate a jar file containing
>> a
>> >> >> large number of files (>= 65536, in practice), then javac becomes
>> unable
>> >> >> to resolve classes from that jar file. This only occurs with jars
>> >> produced
>> >> >> by the Maven jar plugin, and only when the number of files is large
>> (as
>> >> >> demonstrated below).
>> >> >>
>> >> >> An example build, using the maven exec plugin to generate a large
>> >> >> number (65525) of files:
>> >> >>
>> >> >> http://waste.io7m.com/2013/11/12/jarbug.zip
>> >> >
>> >> > Can anyone else reproduce this problem? This would seem to indicate a
>> >> serious
>> >> > bug somewhere. I'm trying to eliminate Maven as a cause.
>> >> >
>> >> > M
>> >> >
>> >> >
Re: Strange issue with generated jars
On Wed, Nov 13, 2013 at 3:32 PM, Curtis Rueden wrote:
> Hi,
>
> org.apache.maven.u...@io7m.com wrote:
> > Can anyone else reproduce this problem?
>
> OK, I ran the example ("mvn clean package") and the project builds
> successfully on my system:
>
>
I ran the sample project on a couple systems with different results.
Fails on:
$ mvn -v
Apache Maven 3.1.1 (NON-CANONICAL_2013-10-11_13-55_root; 2013-10-11
03:55:32-0600)
Maven home: /opt/maven
Java version: 1.6.0_51, vendor: Sun Microsystems Inc.
Java home: /opt/java6/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.11.7-1-ck", arch: "amd64", family: "unix"
Passes on:
$ mvn -v
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
09:22:22-0600)
Maven home: /usr/local/Cellar/maven/3.1.1/libexec
Java version: 1.6.0_65, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac"
@Curtis, I see you use home brew also ;)
So it appears to be JDK bug.
Re: Strange issue with generated jars
On Wed, 13 Nov 2013 11:33:51 -0800 George Wilson wrote: > Unfortunately, my company's security policies do not allow for the > downloading and building of external projects without approval from IT > and security so I cannot really test your code (not without going to a > committee, etc...). Any chance you can post the errors you are > getting? Is this a JVM heap issue perhaps? Have you tried increasing > your Java memory? Just a thought since you mentioned that javac is > what seems to die here. Hello. I appreciate it that executing code run by semi-anonymous people on the internet is generally not a good idea! Here's the full output of 'mvn -X -e clean verify' (gzip compressed, as it's 13mb otherwise): http://waste.io7m.com/2013/11/13/jarbug.log.gz M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange issue with generated jars
Hi,
org.apache.maven.u...@io7m.com wrote:
> Can anyone else reproduce this problem?
OK, I ran the example ("mvn clean package") and the project builds
successfully on my system:
$ mvn -v
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
10:22:22-0500)
Maven home: /usr/local/Cellar/maven/3.1.1/libexec
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.9", arch: "x86_64", family: "mac"
$ jar tf code/target/code-0.1.0.jar |wc
11 11 270
$ jar tf resources/target/resources-0.1.0.jar |wc
65547 65547 2151861
George Wilson wrote:
> the restriction is in regards to building a larger project like a
> maven build.
Well, it's 38 lines of code:
$ find . -name '*.java' | xargs wc
10 18 157 ./code/src/main/java/com/io7m/jarbug/Main.java
28 74 694
./resources/src/main/java/com/io7m/jarbug/MakeSources.java
38 92 851 total
If you just look at it, you can see that it doesn't do anything bad.
> I am not sure that it is really necessary to ask people to go out of
> their way to build VM systems
I am not the OP, and was not asking you to do anything. I was merely
inquiring whether you could perhaps avoid your company's bureaucracy via
some technical means.
> It seems that since you have run this and generated errors, it would
> be easier as a first step diagnostic to post your error messages-
> output cleaned if need be of course.
I agree that it wouldn't hurt for the OP to post his error messages, too.
But that said, IMHO, posting a complete example project demonstrating the
issue is about the *best* thing you can do.
Regards,
Curtis
On Wed, Nov 13, 2013 at 4:16 PM, George Wilson wrote:
> A crippling restriction or not, it is company policy which I do not
> have any authority over. Its one thing to try a snippet from stack
> overflow but the restriction is in regards to building a larger
> project like a maven build. The concern is not being able to evaluate
> what the code or individual scripts do.
> I do not have time right this minute to set up a VM instance but
> perhaps could later on workload permitting. It seems that since you
> have run this and generated errors, it would be easier as a first step
> diagnostic to post your error messages- output cleaned if need be of
> course. FWIW, I am not sure that it is really necessary to ask people
> to go out of their way to build VM systems, when the error output
> might solve the problem immediately.
>
> On Wed, Nov 13, 2013 at 11:37 AM, Curtis Rueden wrote:
> > Hi George,
> >
> > That's a new one on me. Can you build in an isolated VM? On a personal
> > machine while at work? Not being able to try out code from the Internet
> > seems like a crippling restriction to me.
> >
> > -Curtis
> > On Nov 13, 2013 1:34 PM, "George Wilson" wrote:
> >
> >> Unfortunately, my company's security policies do not allow for the
> >> downloading and building of external projects without approval from IT
> >> and security so I cannot really test your code (not without going to a
> >> committee, etc...). Any chance you can post the errors you are
> >> getting? Is this a JVM heap issue perhaps? Have you tried increasing
> >> your Java memory? Just a thought since you mentioned that javac is
> >> what seems to die here.
> >>
> >> On Wed, Nov 13, 2013 at 5:57 AM,
> wrote:
> >> > On Tue, 12 Nov 2013 13:02:46 +
> >> > wrote:
> >> >
> >> >> Hello.
> >> >>
> >> >> I've run into a strange but easily reproduced problem with the jar
> files
> >> >> generated by Maven. Essentially, if I generate a jar file containing
> a
> >> >> large number of files (>= 65536, in practice), then javac becomes
> unable
> >> >> to resolve classes from that jar file. This only occurs with jars
> >> produced
> >> >> by the Maven jar plugin, and only when the number of files is large
> (as
> >> >> demonstrated below).
> >> >>
> >> >> An example build, using the maven exec plugin to generate a large
> >> >> number (65525) of files:
> >> >>
> >> >> http://waste.io7m.com/2013/11/12/jarbug.zip
> >> >
> >> > Can anyone else reproduce this problem? This would seem to indicate a
> >> serious
> >> > bug somewhere. I'm trying to eliminate Maven as a cause.
> >> >
> >> > M
> >> >
> >> > -
> >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: users-h...@maven.apache.org
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional command
Re: Strange issue with generated jars
A crippling restriction or not, it is company policy which I do not have any authority over. Its one thing to try a snippet from stack overflow but the restriction is in regards to building a larger project like a maven build. The concern is not being able to evaluate what the code or individual scripts do. I do not have time right this minute to set up a VM instance but perhaps could later on workload permitting. It seems that since you have run this and generated errors, it would be easier as a first step diagnostic to post your error messages- output cleaned if need be of course. FWIW, I am not sure that it is really necessary to ask people to go out of their way to build VM systems, when the error output might solve the problem immediately. On Wed, Nov 13, 2013 at 11:37 AM, Curtis Rueden wrote: > Hi George, > > That's a new one on me. Can you build in an isolated VM? On a personal > machine while at work? Not being able to try out code from the Internet > seems like a crippling restriction to me. > > -Curtis > On Nov 13, 2013 1:34 PM, "George Wilson" wrote: > >> Unfortunately, my company's security policies do not allow for the >> downloading and building of external projects without approval from IT >> and security so I cannot really test your code (not without going to a >> committee, etc...). Any chance you can post the errors you are >> getting? Is this a JVM heap issue perhaps? Have you tried increasing >> your Java memory? Just a thought since you mentioned that javac is >> what seems to die here. >> >> On Wed, Nov 13, 2013 at 5:57 AM, wrote: >> > On Tue, 12 Nov 2013 13:02:46 + >> > wrote: >> > >> >> Hello. >> >> >> >> I've run into a strange but easily reproduced problem with the jar files >> >> generated by Maven. Essentially, if I generate a jar file containing a >> >> large number of files (>= 65536, in practice), then javac becomes unable >> >> to resolve classes from that jar file. This only occurs with jars >> produced >> >> by the Maven jar plugin, and only when the number of files is large (as >> >> demonstrated below). >> >> >> >> An example build, using the maven exec plugin to generate a large >> >> number (65525) of files: >> >> >> >> http://waste.io7m.com/2013/11/12/jarbug.zip >> > >> > Can anyone else reproduce this problem? This would seem to indicate a >> serious >> > bug somewhere. I'm trying to eliminate Maven as a cause. >> > >> > M >> > >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange issue with generated jars
Hi George, That's a new one on me. Can you build in an isolated VM? On a personal machine while at work? Not being able to try out code from the Internet seems like a crippling restriction to me. -Curtis On Nov 13, 2013 1:34 PM, "George Wilson" wrote: > Unfortunately, my company's security policies do not allow for the > downloading and building of external projects without approval from IT > and security so I cannot really test your code (not without going to a > committee, etc...). Any chance you can post the errors you are > getting? Is this a JVM heap issue perhaps? Have you tried increasing > your Java memory? Just a thought since you mentioned that javac is > what seems to die here. > > On Wed, Nov 13, 2013 at 5:57 AM, wrote: > > On Tue, 12 Nov 2013 13:02:46 + > > wrote: > > > >> Hello. > >> > >> I've run into a strange but easily reproduced problem with the jar files > >> generated by Maven. Essentially, if I generate a jar file containing a > >> large number of files (>= 65536, in practice), then javac becomes unable > >> to resolve classes from that jar file. This only occurs with jars > produced > >> by the Maven jar plugin, and only when the number of files is large (as > >> demonstrated below). > >> > >> An example build, using the maven exec plugin to generate a large > >> number (65525) of files: > >> > >> http://waste.io7m.com/2013/11/12/jarbug.zip > > > > Can anyone else reproduce this problem? This would seem to indicate a > serious > > bug somewhere. I'm trying to eliminate Maven as a cause. > > > > M > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Strange issue with generated jars
Unfortunately, my company's security policies do not allow for the downloading and building of external projects without approval from IT and security so I cannot really test your code (not without going to a committee, etc...). Any chance you can post the errors you are getting? Is this a JVM heap issue perhaps? Have you tried increasing your Java memory? Just a thought since you mentioned that javac is what seems to die here. On Wed, Nov 13, 2013 at 5:57 AM, wrote: > On Tue, 12 Nov 2013 13:02:46 + > wrote: > >> Hello. >> >> I've run into a strange but easily reproduced problem with the jar files >> generated by Maven. Essentially, if I generate a jar file containing a >> large number of files (>= 65536, in practice), then javac becomes unable >> to resolve classes from that jar file. This only occurs with jars produced >> by the Maven jar plugin, and only when the number of files is large (as >> demonstrated below). >> >> An example build, using the maven exec plugin to generate a large >> number (65525) of files: >> >> http://waste.io7m.com/2013/11/12/jarbug.zip > > Can anyone else reproduce this problem? This would seem to indicate a serious > bug somewhere. I'm trying to eliminate Maven as a cause. > > M > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange issue with generated jars
On Tue, 12 Nov 2013 13:02:46 + wrote: > Hello. > > I've run into a strange but easily reproduced problem with the jar files > generated by Maven. Essentially, if I generate a jar file containing a > large number of files (>= 65536, in practice), then javac becomes unable > to resolve classes from that jar file. This only occurs with jars produced > by the Maven jar plugin, and only when the number of files is large (as > demonstrated below). > > An example build, using the maven exec plugin to generate a large > number (65525) of files: > > http://waste.io7m.com/2013/11/12/jarbug.zip Can anyone else reproduce this problem? This would seem to indicate a serious bug somewhere. I'm trying to eliminate Maven as a cause. M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
