Hi Jason,
On Feb 16, 2007, at 7:36 PM, Jason van Zyl wrote:
On 16 Feb 07, at 4:43 PM 16 Feb 07, Eric Brown wrote:
Hi Jason,
On Feb 16, 2007, at 5:29 AM, Jason van Zyl wrote:
[snip]
Project with full test cases that can be easily absorbed will
be taken before anything else anything else. If these are for
fixes and you have unit tests that's great, or if you prefer to
create an integration test then to make this easier I have
created a self-contained, fully working of example of our
integration tests:
http://svn.apache.org/repos/asf/maven/core-integration-testing/
trunk/core-integration-test-sample
or
http://idisk.maven.org/jvanzyl/Public/maven-integration-tests/
core-integration-test-sample.zip
I'm a bit confused. This looks considerably different than what
I see in maven-core-it. The ones in maven-core-it look pretty
straight forward. Are there examples of this new style in the
maven-2.0.x tree? If we use this new style, how do you want us
to submit the test (assuming it won't be part of the patch)?
These are being used for 2.0.x and 2.1.x. The sample comes from
one body of tests used for both. I would like complete test
projects submitted. Zipped up with an URL pointing to them or
attached to JIRA will suffice.
Hm. The "fully working example" provided here does not work.
All the goodies are here:
http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/
I will deploy them tomorrow, I've been working with this stuff so
long it's all on machine and everyone working with it now has it
checked out so I forgot to deploy it. It's all in one tree.
Thanks. That makes things a lot better.
Reason: Unable to download the artifact from any repository ...
org.apache.maven.its:core-integration-testing:pom:1-SNAPSHOT. (And
I've built maven-2.0.x and its artifacts are in my repository,
just not the one defined as the parent in the sample here. And I
tried removing the parent and it still wants core-integraiton-
tests:1.0-SNAPSHOT. I'm not sure how much farther to dig.) A
readme or wiki page to better explain how to use this would be
great...
I probably won't get around to this until later next week but there
are 100 examples.
The example shows many of the things you can check. Every example
we have is here:
http://svn.apache.org/repos/asf/maven/core-integration-testing/
trunk/core-integration-tests/src/test/resources/
Yes, I see.
I need to test quite a few things with multi-module builds.
Preferably I just need to create a few pom.xml files and one or
two dummy sources or resources to verify things are building.
Also, please point me to where this style integration test is
being used in the maven-2.0.x tree? I can't find any good examples.
It's not in the 2.0.x tree, this new setup is used by both trunk
and branch which is why they are located outside the tree.
That is nice.
This style integration test seems considerably more complex than
the maven-core-it tests.
I have not found that to be the case, and you as a user should be
able to use an example and get something working in pretty short
order once I've deployed the POMs. Or better I will just release
them. The are very similar in the way they work using the verifier.
The directory structure is slightly different but as I noted we're
still trying out different things. This is what you get for this rev.
It took me a bit to figure out the example(s). I went to the maven
wiki to add a page about writing tests, but I don't have write
permission.
maven-core-it/README.txt explains what needs to happen nicely in
those style tests. I would have saved a bit of time with equivalent
documentation for the new system.
I copied one of those to start some testing and seems trivial
enough. (Though aside from running "mvn install" and manually
generating the desired output files, I'm not clear on how to run
just one single test with maven-core-it.sh.)
There is no maven-core-it.sh in the new setup and I will remove
them from the branch for the next rev to avoid confusion and I'll
setup an externals definition to pull out the single tree of ITs
along with the particular tree of maven you're working on.
Please.
Cheers,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
