Grzegorz Słowikowski wrote:
> Hi all
> 
> We have a lot of problems with our integration tests, and I would like
> to share out thoughts with you. I saw voting for Maven 2.0.2 has started,
> so this is last minute to change something before 2.0.2.
> 
> 1. I think that the two new phases: before/after-integration-test should
> be renamed to pre/post-integration-test. The prefixes would be similar
> to pre/post-site and pre/post-clean. What do you think?

This is a good point. Since they were only introduced after 2.0.1, we
should rename them.

> 
> 2. We cannot compile our intergation tests sources with maven-compiler-plugin
> because we cannot change compileSourceRoots. Firstly it is readonly, and
> secondly there is no way to set them in configuration in pom file.
> We had to write our own it compiler plugin by copying almost all sources
> from TestCompilerMojo.java.
> What would be the best solution? Changing one of the standard compiler mojos?
> Adding additional generic mojo without "readonly"'s, with possibility to set
> source roots, etc? Maybe something else. I don't like what we had to do - 
> copy/paste a lot of source from one of maven-compiler-plugin mojos.
> 
> Pablo from my team wrote about it today, and Bob Allison here:
>  http://jira.codehaus.org/browse/MCOMPILER-13.

I thought this was too much of a coincidence :)

Use the build-helper-maven plugin from org.codehaus.mojo.

> 3. Now all our artifacts for integration testing (there are lot of them) have 
> "test"
> scope. So they are included in unit testing classpaths too. Would it be ok
> to add another scope - "it" to separate it artifacts from unit testing 
> artifacts?

Not for 2.0.2. We can discuss along with the numerous i-t topics.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to