Skip to content
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

Merged
merged 2 commits into from
Apr 23, 2012

Conversation

marcphilipp
Copy link
Member

  • The junit-dep JARs are now deployed as junit:junit into the Maven repository.
  • The junit:junit-dep artifact only consists of a POM pointing to junit:junit now.

Merging this would fix #332.

@ghost ghost assigned marcphilipp Apr 21, 2012
@marcphilipp
Copy link
Member Author

When using junit:junit-dep, Maven users will get the following warning:

[WARNING] The artifact junit:junit-dep:jar:4.11-SNAPSHOT has been relocated to junit:junit:jar:4.11-SNAPSHOT

<?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>
Copy link
Member

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?

Copy link
Member Author

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.

@dsaff
Copy link
Member

dsaff commented Apr 23, 2012

Looks like almost there. How are we going to find out if we break anyone?

dsaff added a commit that referenced this pull request Apr 23, 2012
Relocate Maven artifact "junit-dep" to "junit"
@dsaff dsaff merged commit fe3d338 into junit-team:master Apr 23, 2012
@dsaff
Copy link
Member

dsaff commented Apr 23, 2012

Merged. Thanks! Suggestions on user beta testing?

@marcphilipp
Copy link
Member Author

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:

  1. People just use junit:junit which used to include the hamcrest classes and reference hamcrest-core.
  2. People use junit:junit and reference a newer version of hamcrest.

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.

@dsaff
Copy link
Member

dsaff commented Apr 23, 2012

Great, thanks!

@marcphilipp
Copy link
Member Author

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? ;-)

@dsaff
Copy link
Member

dsaff commented Apr 23, 2012

Sounds good to me, thanks!

@eugenp
Copy link

eugenp commented Dec 20, 2012

So, on the previosuly reported:
[WARNING] The artifact junit:junit-dep:jar:4.11-SNAPSHOT has been relocated to junit:junit:jar:4.11-SNAPSHOT
Should I still see this when using junit-dep-4.11?
Thanks.

@marcphilipp
Copy link
Member Author

@eugenp Yes, you should. Why do you ask?

@eugenp
Copy link

eugenp commented Dec 22, 2012

I was still getting the message and I wasn't sure if this was fixed or not.
Thanks.
Eugen.

@marcphilipp marcphilipp deleted the fix-mvn-artifacts branch January 3, 2013 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants