Re: surefire plugin 2.3.1

As said, it's still in dev, if you want to get it it's at http://people.apache.org/repo/m2-snapshot-repository cheers Francesco DJP JEAN-PROST Dominique wrote: > > Hello, > > I can't find a release for surefire 2.3.1. Judging from jira, it seems > this version is released, but I can't find i

Re: Backwards incompatibility with 2.0.8?

Hi I'm in this situation as well, only with maven-2.0.7. Reading http://jira.codehaus.org/browse/SUREFIRE-61 I haven't understood if they are taking into account both ordering options (main vs test first)... cheers Francesco Ronn.Chinowutthichai wrote: > > I've worked out what happened. Suref

Re: 2.0.8 broken war build

Paul Benedict-2 wrote: > > Francesco, how did you determine that forking creates the correct > classpath > ordering? > > On Dec 3, 2007 3:16 AM, Francesco Vivoli <[EMAIL PROTECTED]> wrote: > >> >> Hi all >> >> I've just posted a similar issue[*];

RE: Failing test suite with 2.0.8

n in your poms? I'm wondering if a new version of a plugin is > forking the build causing your tests to run twice. Javadoc comes to > mind, but there may be others. > > -Original Message- > From: Francesco Vivoli [mailto:[EMAIL PROTECTED] > Sent: Monday, December 03,

Re: 2.0.8 broken war build

Hi all I've just posted a similar issue[*]; I'm also using war packaging and setting never solved it. I still wonder what happens though... Anyone's got an explanation? Cheers Francesco *: http://www.nabble.com/Failing-test-suite-with-2.0.8-tf4934941s177.html Damien Lecan 2 wrote: > > Simi

Failing test suite with 2.0.8

Hi all A part of my test suite uses a combination of DBUnit and HSQL to test database code. A base class basically reads a location ( using this.getClass().getClassLoader().getResource() ) and populates the database during setup. Everything is shut down on teardown. Now, after upgrading to 2.0.8

Re: How to handle multiple deployments?

des/introduction/introduction-to-profiles.html > > 2007/11/13, Francesco Vivoli <[EMAIL PROTECTED]>: >> >> Hi all >> >> we're developing a project that is likely to be customized on a >> per-installation basis. >> For example users may want to ad

How to handle multiple deployments?

Hi all we're developing a project that is likely to be customized on a per-installation basis. For example users may want to add a functionality that, say, requires jar X, also at compile time. Generally speaking, I need to let users to keep in sync with new versions of the project (still _very_