surefire summary

Hi all, Since today mvn test does not report the list of failed tests at the end. I have: Results : Failed tests: Tests run: 74, Failures: 3, Errors: 0, Skipped: 4 [ERROR] Mojo: org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test FAILED for project:

Re: Jetty and using src/test/webapp

This is not so unusual. Consider that I have a similar issue. I have spring configs that are only used for integration testing. These reside in src/test/resource. When firing up jetty:run it cannot read those resources as defined in my web.xml via classpath:resource. Furthermore, the jetty plugin

Apache snapshot repository metadata incorrect.

Hi all, The metadata served by nexus for http://repository.apache.org/snapshots/ is incorrect for the archetype plugin. (https://repository.apache.org/content/groups/snapshots/org/apache/maven /plugins/maven-archetype-plugin/) metadata contains lots of snapshot versions but only

RE: Jetty and using src/test/webapp

The useTestClasspath configuration option adds test classes and resources to the classpath used by jetty:run. Justin -Original Message- From: Todd Orr [mailto:torr0...@gmail.com] Sent: Friday, May 01, 2009 11:39 AM To: Maven Users List Subject: Re: Jetty and using src/test/webapp This

RE: resources versus assembly

No, the war file stays the same, the configuration files we need for the different environments (OTAP) are inside the tar.gz file. EJC This is where I'm getting hung up - if you have MANY environments, and your tar.gz takes as long as 1 hour to build, why bundle something as small as

Surefire system property which includes a property dynamically created earlier in the lifecycle by another plugin

I am trying to use a property in the systemProperties section of the surefire plugin which was dynamically created earlier in the build lifecycle by another plugin (happens to be the properties-maven-plugin). I know the property is actually being set because I successfully use it elsewhere after

How to deploy a module with multiple classifiers?

I have an Maven module that I have to build out for different environments. There are only a few different files for each, so I use profiles and have used build-helper to create the artifacts for each environment, like: - ABC-1.0-SNAPSHOT.jar - ABC-1.0-SNAPSHOT-tomcat.jar -

How to specify SCM username/password for release plugin?

How can I specify the username/password to be used by the release plugin in the settings.xml file (or other system approach)? Normally this is set in the settings.xml and refereed to elsewhere by it's id but how is this refereed by the SCM? -Dave

Re: how to not deploy sources.jar to artifactory

Exactly what I wanted to (not) see. Thanks again Wendy and Todd too Regards, Gord On Wed, Apr 29, 2009 at 5:26 PM, Wendy Smoak wsm...@gmail.com wrote: On Wed, Apr 29, 2009 at 1:23 PM, Gordon Cody gc...@zafinlabs.com wrote: I know I read this (on someones blog I think) but did not realise I

Adding a directory to maven-surefire-plugin's

Hi - I'm working on transitioning a large multi-module project from Ant to Maven, and have encountered a truly bizarre use case for Surefire. The unit tests in a number of the modules use a fairly elaborate Junit runner framework developed here - logging, configuration file locations, etc are all

Re: How to deploy a module with multiple classifiers?

Shouldn't it name the .pom file the same as the .jar file?  Or is there a different way to deploy ALL of them at the same time somehow.  What are the This sounds like a bug that was reported and fixed in version 2.3 of the install plugin. What version are you using? Depending on what version

Re: Apache snapshot repository metadata incorrect.

I'm not administrator to verify but perhaps, the job to fix metadata isn't scheduled ? On Fri, May 1, 2009 at 6:09 PM, Nord, James jn...@nds.com wrote: Hi all, The metadata served by nexus for http://repository.apache.org/snapshots/ is incorrect for the archetype plugin.

Re: Why is source jar deployed twice during release?

On Fri, May 1, 2009 at 2:30 PM, David Hoffer dhoff...@gmail.com wrote: Why would the release plugin try to deploy a sources jar twice?  It fails the second time of course.  Here is my pom... What did you type, and how do you have the release plugin configured? My guess is that the 'release'

Re: Adding a directory to maven-surefire-plugin's classpath

Whoops - left off classpath from the subject. A. On Fri, May 1, 2009 at 1:27 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Hi - I'm working on transitioning a large multi-module project from Ant to Maven, and have encountered a truly bizarre use case for Surefire. The unit tests in a

[PLEASE TEST] Maven 2.2.0-RC1

Hi everyone, It's that time again. For the 2.2.0 release of Maven, we're trying to keep the number of issues fairly limited to regressions, issues with quite a few votes that are low-hanging fruit, and some sort of strategic issues. We're moving Maven to JDK 1.5 with this release, though the

Project/module dependencies in separate JEE apps

Hi. Here is a simple project 'Root' structure: Root +-A | +-A1 | +-A2 | +-A3 +-B +-B1 +-B2 +-B3 Let's say that A is a JEE web application and B is a backing EJB app. Different modules in A depend on different modules in B. For the sake of simplicity: A1 depends on B1, A2 depends on B2 and

Re: Adding a directory to maven-surefire-plugin's classpath

Hey Andrew, would these help? groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModealways/forkMode workingDirectorytarget/workingDirectory

Re: Adding a directory to maven-surefire-plugin's classpath

Sadly, no - that gets passed to the JVM running the tests. The problem here is that I need it in the classpath of the Maven JVM itself - Surefire's calling junit's Request.aClass(testClass).getRunner() on our test classes before it forks. Really, I need to get the developer to rewrite the code,

Re: How to deploy a module with multiple classifiers?

Thanks for the quick response Wayne, It does sound similar although there the .pom wasn't even produced for some reason. I'm using Maven 2.1.0 which comes with 2.2 of the install plugin. I am really hopeful that this will fix it, but had 2 questions: 1. I am using deploy:deploy-file to deploy

Why is source jar deployed twice during release?

Why would the release plugin try to deploy a sources jar twice? It fails the second time of course. Here is my pom... build plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId

Re: Why is source jar deployed twice during release?

I had actually neglected to specify the release plugin in my pom so I understand the super pom's version and config(none) will be used. Our command line is something like this mvn -PciBuild release:prepare release:perform --batch-mode As we are running on CI server, where ciBuild just adds the

Re: Why is source jar deployed twice during release?

On Fri, May 1, 2009 at 3:24 PM, David Hoffer dhoff...@gmail.com wrote: I had actually neglected to specify the release plugin in my pom so I understand the super pom's version and config(none) will be used. ... I don't know what a 'release' profile is, can you explain? The super pom includes a

Re: Why is source jar deployed twice during release?

Thanks much I had no idea there were these defaults, I will set useReleaseProfile false, that should do the trick. -Dave On Fri, May 1, 2009 at 4:39 PM, Wendy Smoak wsm...@gmail.com wrote: On Fri, May 1, 2009 at 3:24 PM, David Hoffer dhoff...@gmail.com wrote: I had actually neglected to

Re: Apache snapshot repository metadata incorrect.

Thanks for finding that. It's been fixed now. The old repo had some junk versions that were being proxied. It's been cleaned out. We schedule daily cleanups of the snapshots, leaving behind 3 copies for a minimum of 10 days, the snapshots are removed when a release is published.