-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch between MavenDependencyAppender #3
Comments
No, currently not, but there are some other options. If your project is separated in multiple modules (jpa, rest, etc.) you can have one You could also include all your libraries in all your tests. Usually that doesn't cause much trouble. |
Thanks for your response. You're right, it doesn't cause much trouble but sometimes, you want your test configuration to be as clear as possible and your execution as fast as possible ;) |
Yes, of course. You could configure libraries when creating deployments, something like this: @Deployment
public static WebArchive createDeployment() {
JavaArchive jar = ShrinkWrap.create(JavaArchive.class);
// add classes to jar
return ShrinkWrap.create(WebArchive.class)
.addAsLibrary(jar);
.addAsLibrary(additionalLibrary);
} The adapter will then correctly restructure deployment to exploded format. As for the But this is not so simple anymore. |
Is there a simple way to have multiple
MavenDependencyAppender
and to switch between them at the test level?I'm looking for something to be able to run one test with default libs, then run one test with jpa related libs, then run one test with web services related lib and so on.
Thanks for your work!
The text was updated successfully, but these errors were encountered: