I was thinking about extending the harness to read in the dependencies and update the project stub to populate the getDependencyArtifacts() results with those values. I then started thinking that the next thing I'll need is to populate getArtifacts() with some pretend transitive dependencies.
Is the plugin-config.xml file supposed to follow the pom xsd? If so, is there a plan for providing a way to populate other stubs from this file? How much work would it be to extend the model used by the harness to allow extra meta-data to be used for populating stubs? (Something like a field in the dependency element that says direct or transitive for example.) -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 10:59 PM To: Maven Developers List Subject: Re: testing-harness MavenProjectStub Yes, I think it is incorrect. On 14/09/2006, at 12:49 PM, Brian E. Fox wrote: > I'm using the project stub in the testing-harness project. I'm curious > about the decision to default all collections to return strings: > > public Set getArtifacts() > { > return Collections.singleton( "" ); > } > > Wouldn't it make more sense to return an empty set than a set with a > string? I can't see how this would ever work since isn't every use of > the resulting set going to cast the object to an Artifact? > > Anyone able to shed light on this? --------------------------------------------------------------------- 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]
