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

versions not up to date #27

Closed
PascalSchumacher opened this issue Mar 29, 2016 · 5 comments
Closed

versions not up to date #27

PascalSchumacher opened this issue Mar 29, 2016 · 5 comments
Assignees

Comments

@PascalSchumacher
Copy link
Member

The readme claims "The master branch contains examples with the latest released version of AssertJ modules", but the master branch uses assertj-core 2.1.0 and assertj-guava 2.0.0.

@PascalSchumacher PascalSchumacher changed the title version not up to date versions not up to date Mar 29, 2016
@joel-costigliola
Copy link
Member

Yeah this need to be fixed.
I mainly use the branch with the snapshot versions as a test safety net, but for our users we should have the master branch showing the latest capabilities of AssertJ.

@joel-costigliola
Copy link
Member

@PascalSchumacher I have added you as a collaborator of this project.

@PascalSchumacher
Copy link
Member Author

So should we merge the java-8 branch into master?

@joel-costigliola joel-costigliola self-assigned this Apr 2, 2016
@joel-costigliola
Copy link
Member

That's a good idea to be consistent with assertj-core naming, I will introduce a java-7 branch to showcase assertj-core 2.x and other java 7 assertj components.

@joel-costigliola
Copy link
Member

Done.
I might add a with-latest-snapshot-versions-java-7 branch (or java-7-snapshot maybe) to have a branch matching assertj-core 2.x SNAPSHOT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants