-
Notifications
You must be signed in to change notification settings - Fork 30
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
Porting Maven tests to Gradle tests #91
Comments
Hi! @bbaudry, Thank you |
You are right @ABHAY0O7, that's exactly the goal |
Hello @bbaudry @tdurieux
But I need the corresponding command that I can directly invoke from the terminal. Thank you |
There is probably no command for that. You will need to code it. You can do that by taking the classpath and copying all the dependency in the good folder |
Yes, I can code it in my build.gradle and use the task through the command line but, when the users will use the plugin then I have to explicitly tell them to add this
section in their build.gradle file along with the plugin configurations. |
I meant that you can replace this part of the code https://github.com/castor-software/depclean/blob/cbfc3954b429a124d92d18f125aac3daaf0b5f68/depclean-maven-plugin/src/main/java/se/kth/depclean/DepCleanMojo.java#L370 with your own java method that does the same thing. |
This folder includes small Maven projects to be used for testing Depclean with Maven:
https://github.com/castor-software/depclean/tree/master/depclean-maven-plugin/src/test/resources-its/
@ABHAY0O7, can you add build.gradle files for each of these projects, so you can use them to test the Depclean gradle plugin?
The text was updated successfully, but these errors were encountered: