Thanks for the feedback. I'll look at the invoker, although I did like the idea of using junit for the tests. Any opinions/experience regarding shitty-maven-plugin?
That's too bad about mock repository. It seems like it could reduce a lot of work. What's not ready? I can't seem to find a jira project for it. It seems like something I could contribute to. -Dave On Fri, Jan 15, 2010 at 6:29 PM, Stephen Connolly < [email protected]> wrote: > invoker is the best for testing plugins. > > verifier based tests are hard to get to work during release:prepare > release:perform (see the problems I had with surefire 2.5) > > invoker is the current best for plugin testing IMHO > > mock repository plugin is not ready yet > > Sent from my [rhymes with tryPod] ;-) > > On 15 Jan 2010, at 17:44, David Stenglein <[email protected]> > wrote: > > Hello, > > After posting a (hackish) patch in > <http://jira.codehaus.org/browse/MAPPASM-92> > http://jira.codehaus.org/browse/MAPPASM-92 I've decided to do more work on > appassembler to provide a better solution to the problem and perhaps make it > more flexible. It seems to me that before doing any fixing or refactoring, > there should be a good set of integration tests, though. > > Right now, it seems that the tests are more specific to the implementation > of the plugin and I'd like to use the verifier combined with the > mock-repository plugin to test the outputs based on a given pom. > > I haven't really participated in open source projects before and I am > posting here on the recommendation of Trygve. Is it the norm to create Jira > tickets for new work like this? How far do things get broken down? I am used > to fairly fine-grained tickets for tracking development tasks. > > Any input would be welcome. > > Thanks, > Dave > >
