"Created: Today 08:00 AM". That is exactly what I'm talking about.
I would have been happy to ask about donating my code, but it's unclear to me from the referenced JIRA entry whether they're talking about making the regular compile and install plugins do the test artifact generation (plus making sure that surefire can run the tests -- as I said, it didn't seem to be able to run tests from a base class in a separate jar). Personally, I think that this would be a common enough feature that it really belongs in the compile and install plugins, rather than a standalone plugin like the one I developed. e.g. <groupId>my.project</groupId> <artifactId>main-artifact</artifactId> <testArtifactId>main-test-artifact</testArtifactId> and then depend on it in the manner John specified. Dave -----Original Message----- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 20, 2005 3:02 PM To: Maven Users List Subject: Re: [m2] reasons for sticking with maven -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 yeah, that looks like it. I wasn't aware of that issue...too new, I guess :) Thanks, Mark. john Mark Hobson wrote: | Isn't this covered by http://jira.codehaus.org/browse/MNG-932 ? | | Mark | | On 20/09/05, John Casey <[EMAIL PROTECTED]> wrote: | | Another solution might be an attached artifact (logically attached to | the main .jar in the repository via the metadata) that would be | available to other projects...so producing project A might also produce: | | a-version-tests.jar | | and you could then depend on it like such: | | <dependency> | ~ <groupId>some.group</groupId> | ~ <artifactId>a</artifactId> | ~ <version>someVersion</version> | ~ <type>test-jar</type> | ~ <scope>test</scope> | </dependency> | | would that solve the problem? | | -john | | Carsten Ziegeler wrote: | | Dave Neuer wrote: | | | |>Yes, that's a workaround I'm not OK with, so a developer cannot be in | |>/masterProject/projectA and do "m2 test," see BUILD SUCCESSFUL and think | |>that everything is OK and check in a bunch of broken code because no | |>tests | |>were run -- since the tests for A don't live in A. | |> | | | | Oh no, they are still in A - that's trick :) (ok, one could call it | | hack). You have the correct pom for A containing the tests. You make a | | sub directory in project A: "tests-for-b", add a pom.xml there | | referencing the tests of A as src (using "../") and then it works. | | | | | |>Again, I did write a maven-test-artfiact plugin which has a compile and | |>install target; it *does* generate a test artifact (default name | |>${artifactId}-test.${packaging}, but it's configurable. | |> | |>However, it doesn't generate a POM, and even w/ a manually generated | |>one, and a declared dependancy on A's test artifact in project B, | |>surefire doesn't run the tests in the baseclasses which reside in the | |>test.jar. | |> | |>That's where I got, and where I ran out of patience and time to keep | |>going. I'd be happy to ask my manager if we can release this code if | |>someone else were interested in running w/ it. | |> | | | | It would be interesting to hear what the m2 developers say about this | | problem :) | | | | Carsten | | - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] | --------------------------------------------------------------------- | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDMFyrK3h2CZwO/4URAmdkAJ9EtnA8+4q/E1y9vFW/qCzlrPueRgCeJ2Ho OImXL7E2wJ3HxevjML4egXg= =F56A -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
