-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Relocate Maven artifact "junit-dep" to "junit" #421
Conversation
When using junit:junit-dep, Maven users will get the following warning:
|
<?xml version="1.0" encoding="UTF-8"?> | ||
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd "> | ||
<modelVersion>4.0.0</modelVersion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you line up the indentation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Done, see 834dcd7.
Looks like almost there. How are we going to find out if we break anyone? |
Relocate Maven artifact "junit-dep" to "junit"
Merged. Thanks! Suggestions on user beta testing? |
Locally, I created two sample projects, one referencing junit:junit, one referencing junit:junit-dep. When referencing junit:junit-dep, I got a warning, as stated in my previous comment. Instead, junit:junit was referenced as a dependency which will behave exactly as junit:junit-dep before. The sample project referencing junit:junit was also fine. I was able to include a newer Hamcrest release by excluding the dependency to hamcrest-core and instead referencing the newer hamcrest version explicity. For existing real world usage, there are two possible scenarios:
For (1), there shouldn't be a problem at all. In the case of (2), it was just pure luck (i.e. correct order on classpath) that this worked before this change, it can only get better now. |
Great, thanks! |
Regarding beta testing: There were plenty of people interested in this issue over at #332. Thus, I would suggest that I push a snapshot release of the current master and we ask them to test it. Hopefully, we'll get some feedback... what do you think? ;-) |
Sounds good to me, thanks! |
So, on the previosuly reported: |
@eugenp Yes, you should. Why do you ask? |
I was still getting the message and I wasn't sure if this was fixed or not. |
Merging this would fix #332.