maven-2

I'm encountering a very weird problem with Spring (3.0.1.RELEASE), TestNG (5.11) and Maven Surefire (2.5). I have a test class that extends a Spring helper class for testNG so that test context can be loaded from an xml file (that contains some bean definitions). My project was imported into eclipse using m2eclipse (using Import Maven Project) The class run fine in Eclipse TestNG runner. However, it throws this exception with Maven Surefire Caused by: java.lang.ClassCastException: com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl cannot be cast to javax.xml.parsers

I'm just switching my build process to use maven, I can't find the dependency for AdMob on the maven repository site, how can I configure it manually? Such as : <dependencies> <dependency> <groupId>com.google.android</groupId> <artifactId>android</artifactId> <version>2.2.1</version> <scope>provided</scope> </dependency> </dependencies> An easy way to do this is to have the lib in your source tree and use this: ... <dependency> <groupId>some_admob_groupid</groupId> <artifactId>admob</artifactId> <version>admob_version</version> <scope>system</scope> <systemPath>${basedir}/lib/admob.jar<

I am using Netbeans and Maven projects. In some case Netbeans show me compilation failures (red ballon) BUT Maven compile everything without any problem! What can be the reason of this difference. I already checked that both are using the same JDK version. One possible reason could be that you have not added the required jar in your net beans class path. But the jar is being listed in your maven pom.xml Try doing this, do an mvn install once from your command line in your project directory, and then re-open or reload the project in your netbeans IDE (I hope you are using 6.9?). This will

I'm trying to profile application that is run by "mvn jetty:run", when I connect VisualVM to it and click on Profile jetty crashes with: Profiler Agent: Waiting for connection on port 5140 (Protocol version: 8) Profiler Agent: Established local connection with the tool # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6da5e5d4, pid=5124, tid=5704 # # JRE version: 6.0_16-b01 # Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode windows-x86 ) # Problematic frame: # V [jvm.dll+0x1ae5d4] # # An error report file with more

I'm trying to execute my project using the Maven exec:exec goal and I've tried to configure it with this snippet: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.1.1</version> <configuration> <executable>java</executable> <arguments> <argument>-jar ${staging.dir}/project.jar</argument> </arguments> </configuration> <executions> <execution> <goals> <goal>exec</goal> </goals> </execution> </executions> </plugin> When I run mvn exec:exec I get the output: ------------------------------------------------------------------------ [ERROR]BUILD ERROR

In order to clean up something of a giant mess, I set out to put the code of my tests all in one ordinary java project (all in src/main/java), and then declare that as a <scope>test</scope> dependency in another project, and expect the tests to run. No such luck. surefire wants to just run the tests that it can see in the sources. I can see a sadly obvious solution here involving the build-helper-plugin and adding the tests into the test compilation environment as a source directory, but I was hoping to avoid it. In case anyone is wondering, the reason for all this is that the POM