Sounds like a great idea! They should all go in maven-core-it (possibly as multiple projects). This is really the integration testing of the Maven distribution, not just the maven-core library.
- Brett Joakim Erdfelt wrote: > There are a number of issues within JIRA that are the result of > Resource access issues. > > They way I see it, we have 4 different resource access issues when > dealing with plugins/reports. > > 1) resources from dependency in parent pom. > 2) resources from transitive dependency. > 3) resources from plugin/dependencies/dependency. > 4) resources due to dependencyManagement. > > We need to be able to address all of these access vectors from 5 > different paths. > > 1) Direct mojo:goal usage. > 2) Configured mojo:goal in project pom. > 3) Configured mojo:goal in parent pom. > 4) Configured report in project pom. > 5) Configured report in parent pom. > > Would it be wise to create a maven-core-it project (or similar for > reporting) to cover all of these scenarios? > > /* joakim */ > > --------------------------------------------------------------------- > 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]
