My Project has the standard Project structure which is recommended by maven.
scr
|-main
| |-java
| |-resources
|-test
| |-java
| |-resources
under main-resources I have my "real" properties file which has the real mysql-database connection parameters and under test-resources I have a test properties file which points to a in-memory HSQLDB.
When running the JUnit Tests standalone the Test took the test properties file and everything was OK. When running maven with goal Package, the tests failed. I was adding some debug-messages and found out, that maven took the wrong properties file (the "real" properties file).
After a long period of googling around and trying to configure the surefire-plugin I tried to call the target from the console ...
I THINK I'M GOING TO KICK THE m2eclipse PLUGIN SINCE IT IS THE SECOND TIME IT COST ME A LOT OF TIME !
Showing posts with label Maven. Show all posts
Showing posts with label Maven. Show all posts
Thursday, November 29, 2007
Monday, October 15, 2007
Maven Plugin for Eclipse 2
On September 17th the new Version 0.0.11 of m2eclipse was released. This Version DOES fix the bug mentioned on August 16th
Goal "site" now works within Eclipse.
Goal "site" now works within Eclipse.
Thursday, August 16, 2007
Maven Plugin for Eclipse
After migrating my whole Project to maven 2.0 I experienced the following problem with the m2eclipse plugin (latest stable relase 0.0.10):
By running goal "site" I got the following error
Failed to configure plugin parameters for: org.apache.maven.plugins:maven-javadoc-plugin:2.3
on the command line, specify: '-DdocletArtifact=VALUE'
Cause: Class name which was explicitly given in configuration using 'implementation' attribute: 'org.apache.maven.plugin.javadoc.options.DocletArtifact' cannot be loaded
First I thought, I did something wrong with my POM. After googling around and trying some different configuration I found out, that the error occurs only when called from within Eclipse. The command Line call worked perfect.
Seemingly this bug is fixed with version 0.0.11. Because Version 0.0.11 is still a Development Version and the Command Line Call works fine, I will NOT validate this statement. I only wrote this Posting, because when googling for the error message I got no help (except a Chinese Site where I got some translational Problems)
By running goal "site" I got the following error
Failed to configure plugin parameters for: org.apache.maven.plugins:maven-javadoc-plugin:2.3
on the command line, specify: '-DdocletArtifact=VALUE'
Cause: Class name which was explicitly given in configuration using 'implementation' attribute: 'org.apache.maven.plugin.javadoc.options.DocletArtifact' cannot be loaded
First I thought, I did something wrong with my POM. After googling around and trying some different configuration I found out, that the error occurs only when called from within Eclipse. The command Line call worked perfect.
Seemingly this bug is fixed with version 0.0.11. Because Version 0.0.11 is still a Development Version and the Command Line Call works fine, I will NOT validate this statement. I only wrote this Posting, because when googling for the error message I got no help (except a Chinese Site where I got some translational Problems)
Subscribe to:
Posts (Atom)
Posts
